CVE-2024-23055: An issue in Plone Docker Official Image 5.2.13 (5221) open-source software allows for remote code execution...
An issue in Plone Docker Official Image 5.2.13 (5221) open-source software allows for remote code execution via improper validation of input by the HOST headers.
Security readout for executives and security teams
Plain-English summary
CVE-2024-23055 describes possible remote code execution in Plone Docker Official Image 5.2.13 (5221) tied to improper HOST header validation. Business urgency is moderate: it is remotely reachable and unauthenticated per CVSS, but public source data is sparse and requires user interaction.
Executive priority
Treat this as a moderate-priority exposure review. Prioritize internet-facing Plone containers first, then validate vendor guidance before making production changes.
Technical view
The CVE record reports HOST header input validation weakness affecting Plone Docker Official Image 5.2.13 (5221). CVSS 3.1 is 6.1, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. The affected product fields are not populated, and no CWE or vendor fix is provided in the bundle.
Likely exposure
Exposure is most likely where Plone Docker Official Image 5.2.13 (5221) is internet-facing or reachable through a proxy that passes untrusted Host headers. The source bundle does not identify other affected versions.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The bundle includes a public GitHub reference, but does not establish active exploitation, reliable exploit maturity, or weaponized use.
Researcher notes
Evidence is thin: affected vendor/product fields are n/a, no CWE is assigned, and no patch is named. The RCE description should be handled cautiously until validated against the referenced materials and vendor guidance.
Mitigation direction
Inventory deployments using Plone Docker Official Image 5.2.13 (5221).
Check Plone and Docker image guidance for corrected tags or official mitigation.
Avoid exposing affected instances directly to untrusted networks where possible.
Restrict accepted Host headers at trusted ingress controls where operationally feasible.
Monitor application and proxy logs for suspicious Host header activity.
Validation and detection
Confirm container image name, tag, and build identifier in production inventories.
Review ingress and reverse proxy configuration for Host header handling.
Check whether public routes reach affected Plone containers.
Compare deployed image versions against vendor guidance when available.
Document uncertainty where affected product metadata remains incomplete.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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.
description · low confidence lookup
Execution 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.
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.
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.
1CVSS vectors
3Timeline events
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We 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.