Skip to content
Fencer Intel
medium 4.7

CVE-2013-4195 json

Plone Multiple open redirect vulnerabilities

published 12y ago modified 4mo ago also GHSA-j67j-8hrp-76xm , PYSEC-2014-59 , EUVD-2014-0077

cvss
4.7
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

Multiple open redirect vulnerabilities in (1) marmoset_patch.py, (2) publish.py, and (3) principiaredirect.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allow remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.

Patch / fix

  • pypi plone 4.1.1, 4.2.6, 4.3.2

Is CVE-2013-4195 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-4195 updated cvss 4.3

plone: Open redirect in the HTTP server implementation (marmoset_patch.py, publish.py, principiaredirect.py)

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N
GitHub 3.1 4.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
pypi plone
>=2.1, <4.1.1
>=4.2, <4.2.6
>=4.3, <4.3.2
4.1.1
4.2.6
4.3.2

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-601 URL Redirection to Untrusted Site

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.