dbcve.org
PloneApplication

CVE-2024-0669

HIGH · 7.1 CVSS v3.1 Published 2024-01-18
Fix available
A fix is available. Upgrade to 6.0.7 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Cross-Frame Scripting vulnerability has been found on Plone CMS affecting verssion below 6.0.5. An attacker could store a malicious URL to be opened by an administrator and execute a malicios iframe element.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Frame Scripting (XFS) vulnerability in Plone CMS below version 6.0.5 allows attackers to store a malicious URL containing a malicious iframe. When an administrator opens this stored content, the iframe executes, potentially allowing session hijacking, credential theft, or unauthorized actions performed through the victim's authenticated session.

MitigationUpgrade Plone CMS to version 6.0.5 or later to patch the vulnerability. As an interim measure, implement strict Content Security Policy (CSP) headers to block inline iframe execution and apply input validation/sanitization on all user-submitted content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PloneApplication
Affected:< 6.0.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Plone CMS version
    Check the installed Plone version by inspecting the 'Products/Plone/version.txt' file, or log into the Plone admin interface and navigate to 'Site Setup' > 'Version' to view the exact version number.
    Affected if The installed version is below 6.0.7 (e.g., 6.0.5, 6.0.4, 5.1.x, or earlier)
  2. Confirm Plone is network-accessible
    Determine if the Plone instance is accessible over HTTP/HTTPS from the network. Check the server configuration, firewall rules, or attempt to access the Plone site URL from an external host.
    Affected if Plone is publicly or internally accessible and allows user content submissions
  3. Verify user content submission is enabled
    Check if Plone's content creation features are available to non-admin users. Log in as a standard user or anonymous visitor and attempt to create or submit content (e.g., create a page, comment, or upload a file).
    Affected if Standard users, members, or anonymous users can create or submit content to the Plone site
  4. Search for suspicious iframe tags in stored content
    Access the ZODB database or Plone's content management interface. Use the 'Portal Catalog' or search functionality to look for content containing '<iframe>' tags, or query the database directly for iframe references in the HTML content.
    Affected if Any stored content contains iframe tags pointing to untrusted or malicious URLs

You are affected if Plone CMS version is below 6.0.7 and the system accepts user-submitted content that could contain embedded iframes visible to administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.0.7 or later
Fixed in 6.0.7
Interim mitigation

Upgrade Plone CMS to version 6.0.5 or later to patch the vulnerability. As an interim measure, implement strict Content Security Policy (CSP) headers to block inline iframe execution and apply input validation/sanitization on all user-submitted content.

Recommended fix Moderate confidence

Plone 6.0.7 or later

  1. 1. Backup your current Plone installation and database
  2. 2. Review the Plone 6.0.7 release notes for any breaking changes
  3. 3. Upgrade Plone to version 6.0.7 or later
  4. 4. Verify the upgrade was successful by logging into the admin interface
  5. 5. Test that the cross-frame scripting vulnerability is no longer present
Caveat Review Plone 6.0.7 release notes for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Plone Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0669 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0669 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data