Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2012-5488: python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to…

MediumCVSS 5.0 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.6% (FIRST EPSS); higher than 85.6% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: plone (PyPI) 4.3b1, 4.2.3; conga (Red Hat:rhel_cluster:5) 0:0.12.2-81.el5; conga-debuginfo (Red Hat:rhel_cluster:5) 0:0.12.2-81.el5.

Low priority for now. Upgrade to plone (PyPI) 4.3b1, 4.2.3; conga (Red Hat:rhel_cluster:5) 0:0.12.2-81.el5; conga-debuginfo (Red Hat:rhel_cluster:5) 0:0.12.2-81.el5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

Published
Sep 30, 2014
Updated
Jun 16, 2026
EPSS
2.6% · 85th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.6%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2012-5488

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for plone records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
ploneplone

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • plone ploneup to 4.2.2 inclusive
  • plone plone1.0
  • plone plone1.0.1
  • plone plone1.0.2
  • plone plone1.0.3
  • plone plone1.0.4
  • plone plone1.0.5
  • plone plone1.0.6
+12 more rows
  • plone plone2.0
  • plone plone2.0.1
  • plone plone2.0.2
  • plone plone2.0.3
  • plone plone2.0.4
  • plone plone2.0.5
  • plone plone2.1
  • plone plone2.1.1
  • plone plone2.1.2
  • plone plone2.1.3
  • plone plone2.1.4
  • plone plone2.5

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIplonefrom 4.3a0 · before 4.3b14.3b1
PyPIplonebefore 4.2.34.2.3
Red Hat:rhel_cluster:5congabefore 0:0.12.2-81.el50:0.12.2-81.el5
Red Hat:rhel_cluster:5conga-debuginfobefore 0:0.12.2-81.el50:0.12.2-81.el5
Red Hat:rhel_cluster:5lucibefore 0:0.12.2-81.el50:0.12.2-81.el5
Red Hat:rhel_cluster:5riccibefore 0:0.12.2-81.el50:0.12.2-81.el5

Same product

plone: all records

Other highest-scoring records for the same primary product.

  • CVE-2011-3587Unspecified vulnerability in Zope 2.12.x and 2.13.x, as used in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2, allows remote…
    60This week
  • CVE-2021-33509Plone through 5.2.4 allows remote authenticated managers to perform disk I/O via crafted keyword arguments to the ReStructuredText…
    40Plan
  • CVE-2020-35190The official plone Docker images before version of 4.3.18-alpine (Alpine specific) contain a blank password for a root user.
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2012-5486Sep 30, 2014 · ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject…
    26Monitor
  • ← EarlierCVE-2012-5487Sep 30, 2014 · The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with…
    35Monitor
  • Later →CVE-2012-5489Sep 30, 2014 · The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3…
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
PyPI:plone4.2.3Package registry (OSV)
PyPI:plone4.3b1Package registry (OSV)
red hat:conga0:0.12.2-81.el5 · Red Hat:rhel_cluster:5Package registry (OSV)
red hat:conga-debuginfo0:0.12.2-81.el5 · Red Hat:rhel_cluster:5Package registry (OSV)
red hat:luci0:0.12.2-81.el5 · Red Hat:rhel_cluster:5Package registry (OSV)
red hat:ricci0:0.12.2-81.el5 · Red Hat:rhel_cluster:5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

Weakness class (CWE)

CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVSS vector

AV:N/AC:L/Au:N/C:N/I:N/A:P

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records