Cyber Resilience

CVE-2024-37732

XSS in Anchorcms Anchor Cms 0.12.7

Public PoCXSS
Published
24 June 2024
Modified
21 November 2024
CVSS Score v3.1 6.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.17 97th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-37732 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Anchorcms Anchor Cms. Its CVSS base score is 6.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-37732 is a cross-site scripting vulnerability, tracked under CWE-79 and CWE-80, that affects Anchor CMS version 0.12.7. The flaw permits a remote attacker to execute arbitrary code through upload or processing of a specially crafted PDF file and carries a CVSS 3.1 base score of 6.1 reflecting network attack vector, low complexity, no required privileges, required user interaction, and changed scope with limited impacts on confidentiality and integrity.

An unauthenticated remote attacker can exploit the issue by supplying the malicious PDF to an Anchor CMS instance; successful exploitation results in script execution within the context of another user’s session, enabling actions such as data theft or interface manipulation without affecting availability.

Public references consist of two Gitee issue reports that document the finding, though they contain no published patches or explicit mitigation guidance at the time of disclosure. The associated EPSS score has remained flat at 0.1395 with no material increase since publication.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Cross Site Scripting vulnerability in Anchor CMS v.0.12.7 allows a remote attacker to execute arbitrary code via a crafted .pdf file.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34033Shared CWE-79, CWE-80
CVE-2024-49337Shared CWE-79, CWE-80
CVE-2024-45406Shared CWE-79, CWE-80
CVE-2023-47869Shared CWE-79, CWE-80
CVE-2025-25299Shared CWE-79, CWE-80
CVE-2024-6052Shared CWE-79, CWE-80
CVE-2023-30615Shared CWE-79, CWE-80
CVE-2023-20257Shared CWE-79, CWE-80
CVE-2024-42195Shared CWE-79, CWE-80
CVE-2024-28832Shared CWE-79, CWE-80

Affected Assets

anchorcms
anchor cms
0.12.7

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2
  • V1.2.1
  • V1.3.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.

Input validation directly enforces neutralization of untrusted data before it reaches web output generation.

Output filtering can catch or sanitize unneutralized script content before it is served to users.

Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

prevents

Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.

prevents

Application security requirements explicitly call for neutralization of script-related HTML tags.

prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

References