Code execution via unclaimed npm dependency
Published Feb 5, 2024 · Updated Jul 9, 2026
Dependency confusion in Plone Docker Official Image 5.2.13 allows remote attackers to execute code through tinymce-builded. The bundled ++plone++static/components metadata names the unclaimed tinymce-builded npm package, allowing an attacker who registers that name to supply malicious package content. Execution requires a build or dependency install to resolve and run that package; the evidence does not show exploitation through a running Plone HTTP service.
Summary
What happened
Dependency confusion in Plone Docker Official Image 5.2.13 allows remote attackers to execute code through tinymce-builded. The bundled ++plone++static/components metadata names the unclaimed tinymce-builded npm package, allowing an attacker who registers that name to supply malicious package content. Execution requires a build or dependency install to resolve and run that package; the evidence does not show exploitation through a running Plone HTTP service.
The record
- CVE
- CVE-2024-23054
- Published
- Feb 5, 2024
- Updated
- Jul 9, 2026
- Vendor
- Plone
- Product
- Plone Docker Official Image
- Classifications
- CWE-427, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2.13
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Dependency Confusion Proof of Conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo