Skip to content
Fencer Intel
medium 4.3

CVE-2013-4198 json

Plone's authenticated users able to alter their password despite of policy definition

published 12y ago modified 4mo ago also GHSA-qjxf-6pr8-j87v , PYSEC-2014-62 , EUVD-2014-0080

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

Summary

mail_password.py in Plone 2.1 through 4.1, 4.2.x through 4.2.5, and 4.3.x through 4.3.1 allows remote authenticated users to bypass the prohibition on password changes via the forgotten password email functionality.

Patch / fix

  • pypi plone 4.1.1, 4.2.6, 4.3.2

Is CVE-2013-4198 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-4198 updated cvss 3.5

plone: Authenticated users able to alter their password despite of policy definition / setting prohibiting it (mail_password.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.12% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

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

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-863 Incorrect Authorization

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.