Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-28741 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Chebuya (inferred from references). Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 0.5% 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 SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — 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-28741 is a stored cross-site scripting vulnerability (CWE-79) affecting the login.php component of NorthStar C2 version 1, an open-source command-and-control framework available on GitHub. The flaw permits unauthenticated remote attackers to inject malicious scripts that execute in the context of other users or agents interacting with the C2 server. It carries a CVSS 3.1 base score of 8.8, reflecting network attack vector, low complexity, and impacts that can reach confidentiality, integrity, and availability.
An attacker can deliver a crafted payload to the login page that is stored and later executed by NorthStar C2 agents or operators. Successful exploitation chains the XSS into remote code execution on the agents, allowing arbitrary command execution without prior authentication.
Public references, including a detailed technical write-up and a PacketStorm entry, describe the issue as pre-authentication stored XSS that directly leads to RCE on connected agents. The associated EPSS score stands at 0.8799 with no subsequent rise, indicating sustained exploitation interest since disclosure. No vendor patches or official mitigation guidance appear in the referenced materials.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-25830
Vulnerability Data
Cross Site Scripting vulnerability in EginDemirbilek NorthStar C2 v1 allows a remote attacker to execute arbitrary code via the login.php component.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation and sanitization of all inputs to login.php, blocking storage of malicious XSS payloads before they can be executed.
Requires filtering of information outputs from the C2 server so that stored script payloads cannot execute in agent or operator browsers.
Deploys malicious-code protections that can recognize and block common XSS delivery patterns or resulting agent RCE behavior.
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.
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).
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.
Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.
Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.
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.
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.
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.
Webpage malware scanning and block-listing of known malicious sites reduce the likelihood that reflected or stored script payloads reach a user’s browser.