Security readout for executives and security teams
Plain-English summary
CVE-2024-23054 is reported as a critical remote code execution issue involving Plone Docker Official Image 5.2.13 (5221). The concern is a missing public npm package reference, which could create dependency confusion risk. The public record does not provide a confirmed patch version or broad affected-product matrix.
Executive priority
Treat this as urgent for any externally reachable or production Plone deployment using the named Docker image. The CVSS score is critical, but confidence is constrained because the public source bundle lacks a vendor patch statement and detailed affected-product data.
Technical view
The CVE describes a package listed under ++plone++static/components that does not exist in the public npm index. The record maps this to CWE-427 and CVSS 9.8, with network attack vector and no required privileges or user interaction. Detailed vendor remediation evidence is not present in the provided sources.
Likely exposure
Exposure is most likely where Plone Docker Official Image 5.2.13 (5221) is built, deployed, mirrored, or used as a base image. Because the CVE affected-product fields are listed as n/a, confirm exposure through container image tags, SBOMs, build logs, and deployment inventory.
Exploitation context
The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The stated risk is remote code execution from a missing npm package reference, consistent with dependency confusion or unsafe package resolution concerns, but exploit maturity is not established by the provided evidence.
Researcher notes
The key research gap is authoritative vendor detail. The CVE record names Plone Docker Official Image 5.2.13 (5221) and a missing npm package reference, but affected CPEs, fixed versions, and exploitation evidence are absent from the provided bundle.
Mitigation direction
- Check official Plone and Docker image guidance for a fixed or withdrawn image.
- Avoid new deployments of Plone Docker Official Image 5.2.13 (5221).
- Pin dependencies to trusted internal sources during image builds.
- Review mirrors and base images for inherited use of the affected image.
- Restrict network exposure for affected Plone containers until remediation is confirmed.
Validation and detection
- Inventory running containers and image registries for Plone 5.2.13 (5221).
- Review SBOMs and build logs for ++plone++static/components package resolution.
- Confirm whether builds can pull packages from public npm unintentionally.
- Check vulnerability scanner results against CVE-2024-23054 and image digest.
- Document compensating controls where replacement is not immediately possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-427: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-23054 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/c0d3x27/CVEs/blob/main/CVE-2024-23054/README.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Search Path Element
Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.