Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: = 5.0.0
Patched in 5.0.1
Vulnerable: >= 4.0.0, <= 4.1.2
Patched in 4.1.3
Vulnerable: <= 3.2.2
Patched in 3.2.3
Details
When creating content with a very large title or description field, Plone can become unresponsive. Even if the content loads, it can be hard to edit or delete, because the UI is unwieldy.
The problem has been patched in plone.app.dexterity.
plone.app.dexterity 5.0.1.plone.app.dexterity 4.1.3.plone.app.dexterity 3.2.3.Another part of this problem has been patched in plone.app.contenttypes. See this advisory.
There are no known workarounds.
This problem was responsibly reported by Aldin Visnjic to the Plone/Zope Security Team. Thank you!
Note: The Plone/Zope Security team felt that the kind of fixes that were needed could be disruptive in corner cases if they were not careful. So they decided to develop the fixes publicly, giving the whole community the chance the review, and giving them the benefit from early feedback.
EPSS, exploit probability
Low0.76%
estimated chance of real-world exploitation in the next 30 days, higher than 55.6% of every CVE FIRST.org scores
Refreshed 11/8/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.