CVE-2025-10332VulnerabilityPublished 13 Sep 2025Updated 15 Sep 2025

CVE-2025-10332: cdevroe unmark · Cross Site Scripting

Affects cdevroe unmarkSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Sep 2025
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-25.

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
cdevroe unmark	Affected =1.9.0 =1.9.1 =1.9.2 =1.9.3	Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Immediately restrict external access to the unmark application by enforcing network-level controls such as VPNs or IP whitelisting to limit exposure to trusted users only. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting the 'Title' parameter, focusing on common XSS payload signatures. 3) Conduct thorough input validation and output encoding on the 'Title' parameter within any custom integrations or front-end code if possible, to neutralize malicious scripts. 4) Educate users about the risks of clicking on untrusted links or opening suspicious bookmarks within unmark, reducing the likelihood of successful user interaction exploitation. 5) Monitor application logs and network traffic for unusual activity indicative of attempted XSS exploitation. 6) Consider deploying Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing the application. 7) Plan for an upgrade or migration to a patched or alternative solution once available, and maintain communication with the vendor or community for updates. These targeted measures go beyond generic advice by focusing on access control, detection, and user awareness tailored to the specific vulnerability context.

Description

A vulnerability was found in cdevroe unmark up to 1.9.3. Impacted is an unknown function of the file application/views/marks/info.php. Performing manipulation of the argument Title results in cross site scripting. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using cdevroe unmark versions 1.9.0 to 1.9.3, this vulnerability poses a moderate risk. Since unmark is a bookmarking and link management tool, it is often used by individuals and teams to organize and share web resources. Exploitation could allow attackers to execute arbitrary scripts in users' browsers, leading to session hijacking, theft of sensitive information, or unauthorized actions within the application. This could compromise user accounts and potentially expose internal or confidential data if the application is integrated with other internal systems. The remote exploitability without authentication increases the risk, especially in environments where unmark is accessible over the internet. The lack of vendor response and patch availability means organizations must rely on alternative mitigations. The impact on availability is minimal, but the confidentiality and integrity of user data and sessions are at risk. European organizations with remote or public-facing deployments of unmark are particularly vulnerable, especially those in sectors with strict data protection regulations like GDPR, where data breaches can lead to significant legal and financial consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Sep 2025, 00:36 UTC

Technical details

References

Community reviews

Related threats