CVE-2025-9168VulnerabilityPublished 19 Aug 2025

CVE-2025-9168: SolidInvoice · Cross Site Scripting

Affects SolidInvoiceSource 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.3% chance of exploitation in 30 days – higher than 23% 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 19 Aug 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
SolidInvoice	Affected =2.0 =2.1 =2.2 =2.3 =2.4.0	Fixed in–

AI-suggested

Organizations should immediately assess their use of SolidInvoice and identify if affected versions (2.0 through 2.4.0) are in deployment. Input validation and output encoding should be enforced at the application level if source code access and modification are possible. Restricting access to the invoicing system to trusted networks or VPNs can reduce exposure. User education to recognize suspicious invoice-related links or behaviors can help mitigate social engineering attempts leveraging this vulnerability. Monitoring web server logs for unusual requests to the /invoice endpoint and anomalous client-side script execution can aid in early detection. Organizations should also consider isolating the invoicing system from critical internal networks to limit lateral movement in case of compromise. Finally, engaging with the vendor or community for updates or patches and planning for an upgrade once a fix is available is essential.

Description

A vulnerability was found in SolidInvoice up to 2.4.0. This issue affects some unknown processing of the file /invoice of the component Invoice Creation Module. The manipulation of the argument Client Name results in cross site scripting. The attack may be launched 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 SolidInvoice, this vulnerability poses a risk of client-side attacks that could compromise user sessions and expose sensitive financial data. Since invoicing systems are integral to business operations, successful exploitation could disrupt business workflows, lead to data breaches involving client information, and damage organizational reputation. The medium severity suggests that while the vulnerability is not critical, it still presents a tangible risk, especially in environments where multiple users access the invoicing system via web browsers. Attackers could exploit this vulnerability to perform phishing attacks, steal authentication tokens, or manipulate invoice data, potentially leading to financial fraud or compliance violations under regulations such as GDPR. The lack of vendor response and absence of patches increases the risk exposure for organizations relying on this software. Additionally, the remote attack vector means that attackers do not need internal access, increasing the threat surface for organizations with externally accessible invoicing portals.

Summary

CVE-2025-9168 is a cross-site scripting (XSS) vulnerability identified in SolidInvoice versions up to 2.4.0, specifically within the Invoice Creation Module's /invoice endpoint. The vulnerability arises due to improper sanitization or validation of the 'Client Name' parameter, which can be manipulated by an attacker to inject malicious scripts. This flaw allows an attacker to craft a specially crafted request that, when processed by the vulnerable endpoint, results in the execution of arbitrary JavaScript code in the context of the victim's browser. The attack vector is remote and does not require prior authentication, although it requires some user interaction (UI:P) to trigger the malicious payload. The CVSS 4.0 score of 5.1 reflects a medium severity level, indicating moderate impact primarily on confidentiality and integrity with limited impact on availability. The vulnerability does not require privileges but does require user interaction, and the scope is unchanged, meaning the exploit affects only the vulnerable component without extending to other system components. The vendor has been contacted but has not responded or provided a patch, and no known exploits are currently observed in the wild. This vulnerability could be leveraged for session hijacking, credential theft, or delivering further malware through the victim's browser, especially targeting users who interact with the invoicing system. Given the nature of invoicing software, which often contains sensitive financial and client data, exploitation could lead to data leakage or unauthorized actions within the invoicing platform.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Aug 2025, 01:14 UTC

Technical details

References

Community reviews

Related threats