CVE-2025-68457VulnerabilityPublished 19 Dec 2025Updated 13 Jan 2026

CVE-2025-68457: boscop-fr orejime · Cross-site Scripting

Affects boscop-fr orejimeSource CVE Database V5

Not known to be exploited · CVSS 0.6 Low : upgrade to 2.3.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

0.6Low

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

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

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

Base metrics

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

Threat metrics

Exploit Maturity: Unreported

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: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent 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 Subsequent 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: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · 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 19 Dec 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

Upgrade boscop-fr/orejime to 2.3.2.

Affected software

Product	Affected	Fixed in
GitHubboscop-fr/orejime`pkg:github/boscop-fr/orejime`Other threats	Affected <2.3.2	Fixed in 2.3.2

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

AI-suggested

1. Upgrade Orejime to version 2.3.2 or later immediately to apply the official patch that addresses this vulnerability. 2. Implement strict input validation and sanitization on all user-supplied content, especially any HTML or attributes that could be converted into executable code. Use well-established libraries or frameworks for sanitization that specifically neutralize 'javascript:' URIs and other executable content. 3. Employ Content Security Policy (CSP) headers to restrict the execution of inline scripts and limit the sources of executable code in the browser context. 4. Conduct regular security code reviews and penetration testing focused on client-side injection vectors in web applications using Orejime. 5. Educate developers and administrators about the risks of improper attribute handling and the importance of sanitizing dynamic content. 6. Monitor web application logs and user reports for signs of suspicious activity or attempted XSS exploitation. 7. If upgrading Orejime is not immediately possible, apply temporary server-side sanitization filters to remove or neutralize potentially dangerous attributes before rendering pages.

Description

Orejime is a consent manager that focuses on accessibility. On HTML elements handled by Orejime prior to version 2.3.2, one could run malicious code by embedding `javascript:` code within data attributes. When consenting to the related purpose, Orejime would turn data attributes into unprefixed ones (i.e. `data-href` into `href`), thus executing the code. This shouldn't have any impact on most setups, as elements handled by Orejime are generally hardcoded. The problem would only arise if somebody could inject HTML code within pages. The problem has been patched in version 2.3.2. As a workaround, the problem can be fixed outside of Orejime by sanitizing attributes which could contain executable code.

Impact

For European organizations, the impact of this vulnerability is generally low but context-dependent. If an organization uses Orejime versions prior to 2.3.2 in web applications that allow user-supplied content or insufficiently sanitized inputs, attackers could exploit this XSS vulnerability to execute malicious scripts in users' browsers. This could lead to session hijacking, unauthorized actions, or phishing attacks targeting users of the affected web applications. However, since Orejime elements are typically hardcoded and the vulnerability requires HTML injection, the attack surface is limited. Organizations with high compliance requirements for user privacy and consent management, such as those in the EU under GDPR, may face reputational damage or regulatory scrutiny if such vulnerabilities are exploited. The low CVSS score indicates limited direct impact on system confidentiality, integrity, or availability, but the risk to user data and trust remains. The absence of known exploits reduces immediate risk but does not eliminate the need for remediation.

Summary

CVE-2025-68457 is a cross-site scripting vulnerability identified in Orejime, a consent management tool developed by boscop-fr that emphasizes accessibility. The vulnerability arises from improper neutralization of input during web page generation (CWE-79). Specifically, in Orejime versions before 2.3.2, HTML elements managed by Orejime could be manipulated if an attacker managed to inject malicious HTML containing data attributes with embedded 'javascript:' URIs. When a user consents to the related purpose, Orejime converts these data attributes (e.g., 'data-href') into standard attributes (e.g., 'href'), causing the embedded JavaScript to execute in the user's browser context. This execution can lead to theft of session tokens, unauthorized actions, or other malicious behaviors typical of XSS attacks. However, the exploitability is limited because Orejime elements are generally hardcoded, making HTML injection a prerequisite for exploitation. The vulnerability has been addressed in Orejime version 2.3.2 by preventing such attribute conversion or sanitizing inputs. The CVSS 4.0 score of 0.6 reflects a low severity due to the need for user interaction, lack of authentication requirement, and limited scope of affected systems. No active exploits have been reported. Mitigation outside of updating Orejime includes sanitizing any user-controllable attributes that could be converted into executable attributes to prevent script execution.

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 14 Jan 2026, 00:39 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats