CVE-2024-49210VulnerabilityPublished 22 Oct 2024Updated 30 Oct 2024

CVE-2024-49210: n/a

Source CVE Database V5

Not known to be exploited · CVSS 5.2 Medium · fixed in 2024.09 : update affected systems when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.2Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2024.09

CVSS:3.1/AC:L/AV:N/A:N/C:H/I:L/PR:H/S:U/UI:R

Attack Complexity: Low
Attack Vector: Network
Availability: None
Confidentiality: High
Integrity: Low
Privileges Required: High
Scope: Unchanged
User Interaction: Required

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. 2. Implement strict input validation and output encoding on all user-supplied data within the Archer Platform, especially on the iView List UX pages, to prevent injection of malicious scripts. 3. Deploy Content Security Policy (CSP) headers to restrict the execution of untrusted scripts and reduce the impact of potential XSS attacks. 4. Educate users on the risks of clicking unsolicited links and implement phishing awareness training to reduce the likelihood of successful social engineering. 5. Use web application firewalls (WAFs) with rules designed to detect and block reflected XSS attack patterns targeting the Archer Platform. 6. Conduct regular security assessments and penetration testing focused on web application vulnerabilities to identify and remediate similar issues proactively. 7. Restrict access to Archer Platform interfaces to trusted networks or VPNs where feasible to reduce exposure to unauthenticated attackers. 8. Review and harden session management controls to limit the impact of stolen session tokens, including short session lifetimes and multi-factor authentication where supported.

Description

Reflected XSS was discovered in an iView List Archer Platform UX page in Archer Platform 6.x before version 2024.09. A remote unauthenticated attacker could potentially exploit this by tricking a victim application user into supplying malicious HTML or JavaScript code to the vulnerable web application; the malicious code is then reflected back to the victim and executed by the web browser in the context of the vulnerable web application.

Impact

The primary impact of CVE-2024-49210 is on the confidentiality of data handled by the Archer Platform, as successful exploitation can lead to theft of session tokens, user credentials, or other sensitive information accessible within the victim's browser session. This could enable attackers to impersonate users or escalate privileges indirectly. The integrity impact is low but present, as attackers might manipulate client-side interactions or inject misleading content. Availability is not affected. Since the vulnerability is reflected XSS, exploitation requires user interaction, typically through social engineering techniques such as phishing emails containing malicious links. The scope is limited to users who access the vulnerable Archer Platform web interface. Organizations worldwide using Archer Platform 6.x for governance, risk, and compliance management could face targeted attacks aiming to compromise user sessions or harvest sensitive data. This may lead to regulatory compliance failures, data breaches, and erosion of trust in critical risk management systems. Although no known exploits are currently reported, the medium severity score and the widespread use of Archer Platform in enterprise environments underscore the importance of timely mitigation.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 00:24 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats