CVE-2024-0721VulnerabilityPublished 19 Jan 2024Updated 9 Jun 2025

CVE-2024-0721: Jspxcms · Cross Site Scripting

Affects JspxcmsSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.5Low

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

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).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
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.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jan 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

Affected software

Product	Affected	Fixed in
Mavenorg.jspxcms/jspxcms`pkg:maven/org.jspxcms/jspxcms`Other threats	Affected =10.2.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately review their use of Jspxcms version 10.2.0 and specifically audit the Survey Label Handler component for untrusted input handling. Until an official patch is released, applying strict input validation and output encoding on all user-supplied data in survey labels is critical. Web Application Firewalls (WAFs) should be configured to detect and block common XSS payloads targeting survey-related endpoints. Additionally, implementing Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting the sources from which scripts can be loaded. Organizations should also educate users about the risks of interacting with untrusted content and monitor logs for suspicious activities related to survey interactions. Finally, upgrading to a patched version of Jspxcms once available is essential to fully remediate the vulnerability.

Description

A vulnerability has been found in Jspxcms 10.2.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Survey Label Handler. The manipulation leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-251545 was assigned to this vulnerability.

Impact

For European organizations using Jspxcms 10.2.0, this vulnerability could lead to targeted attacks against users interacting with survey components on their websites. While the direct impact on confidentiality and availability is low, the integrity of user interactions and trust in the affected web applications could be compromised. This could result in reputational damage, especially for organizations in sectors such as education, government, or public services that rely on surveys for data collection and citizen engagement. Additionally, attackers could use the XSS vulnerability as a stepping stone for more sophisticated social engineering or session hijacking attacks, potentially leading to unauthorized actions or data manipulation. The requirement for some privilege and user interaction limits the scope but does not eliminate risk, particularly in environments where users have elevated roles or where social engineering can be effective.

Summary

CVE-2024-0721 is a Cross Site Scripting (XSS) vulnerability identified in version 10.2.0 of Jspxcms, specifically within an unspecified functionality of the Survey Label Handler component. This vulnerability allows an attacker to inject malicious scripts that execute in the context of a victim's browser session when interacting with the affected component. The vulnerability is remotely exploitable, requiring low attack complexity but does require the attacker to have some level of privileges (PR:L) and user interaction (UI:R) to trigger the exploit. The CVSS 3.1 base score is 3.5, indicating a low severity level. The impact primarily affects the integrity of the user interface by allowing script injection, but does not compromise confidentiality or availability. No public exploits are currently known to be in the wild, and no patches have been published yet. The vulnerability is classified under CWE-79, which is a common web application security issue related to improper input validation and output encoding in web applications. Given the nature of Jspxcms as a content management system, this vulnerability could be leveraged to conduct phishing attacks, session hijacking, or defacement by injecting malicious JavaScript code into survey labels that other users might view.

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

Affected software

Description

AI analysisMachine-generated, updated 11 Jul 2025, 00:03 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats