CVE-2013-4193
Last modified
CVE-2013-4193 is a vulnerability of currently unknown severity. typeswidget.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly enforce the immutable setting on unspecified content edit forms, which allows remote attackers to hide fields on the forms via a crafted URL.. EPSS estimates a 1.18% chance of exploitation in the next 30 days.
Description
typeswidget.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 does not properly enforce the immutable setting on unspecified content edit forms, which allows remote attackers to hide fields on the forms via a crafted URL.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Plone | Plone | 2.1 |
| Plone | Plone | 2.1.1 |
| Plone | Plone | 2.1.2 |
| Plone | Plone | 2.1.3 |
| Plone | Plone | 2.1.4 |
| Plone | Plone | 2.5 |
| Plone | Plone | 2.5.1 |
| Plone | Plone | 2.5.2 |
| Plone | Plone | 2.5.3 |
| Plone | Plone | 2.5.4 |
| Plone | Plone | 2.5.5 |
| Plone | Plone | 3.0 |
| Plone | Plone | 3.0.1 |
| Plone | Plone | 3.0.2 |
| Plone | Plone | 3.0.3 |
| Plone | Plone | 3.0.4 |
| Plone | Plone | 3.0.5 |
| Plone | Plone | 3.0.6 |
| Plone | Plone | 3.1 |
| Plone | Plone | 3.1.1 |
| Plone | Plone | 3.1.2 |
| Plone | Plone | 3.1.3 |
| Plone | Plone | 3.1.4 |
| Plone | Plone | 3.1.5.1 |
| Plone | Plone | 3.1.6 |
| Plone | Plone | 3.1.7 |
| Plone | Plone | 3.2 |
| Plone | Plone | 3.2.1 |
| Plone | Plone | 3.2.2 |
| Plone | Plone | 3.2.3 |
| Plone | Plone | 3.3 |
| Plone | Plone | 3.3.1 |
| Plone | Plone | 3.3.2 |
| Plone | Plone | 3.3.3 |
| Plone | Plone | 3.3.4 |
| Plone | Plone | 3.3.5 |
| Plone | Plone | 4.0 |
| Plone | Plone | 4.0.1 |
| Plone | Plone | 4.0.2 |
| Plone | Plone | 4.0.3 |
| Plone | Plone | 4.0.4 |
| Plone | Plone | 4.0.5 |
| Plone | Plone | 4.0.6.1 |
| Plone | Plone | 4.1 |
| Plone | Plone | 4.2 |
| Plone | Plone | 4.2.1 |
| Plone | Plone | 4.2.2 |
| Plone | Plone | 4.2.3 |
| Plone | Plone | 4.2.4 |
| Plone | Plone | 4.2.5 |
Showing 50 of 52 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-4193?
How severe is CVE-2013-4193?
How do I fix CVE-2013-4193?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-4187The Flippy module 7.x-1.x before 7.x-1.2 for Drupal does not…6.5
- CVE-2013-4188traverser.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, …
- CVE-2013-4189Multiple unspecified vulnerabilities in (1) dataitems.py, (2…
- CVE-2013-4190Multiple cross-site scripting (XSS) vulnerabilities in (1) s…
- CVE-2013-4191zip.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.…
- CVE-2013-4192sendto.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and…
- CVE-2013-4194The WYSIWYG component (wysiwyg.py) in Plone 2.1 through 4.1,…
- CVE-2013-4195Multiple open redirect vulnerabilities in (1) marmoset_patch…
- CVE-2013-4196The object manager implementation (objectmanager.py) in Plon…
- CVE-2013-4197member_portrait.py in Plone 2.1 through 4.1, 4.2.x through 4…
- CVE-2013-4198mail_password.py in Plone 2.1 through 4.1, 4.2.x through 4.2…
- CVE-2013-4199(1) cb_decode.py and (2) linkintegrity.py in Plone 2.1 throu…
Are you affected by CVE-2013-4193?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST