VulnerabilityPublished 19 Aug 2025

CVE-2025-9171: SolidInvoice · Cross-site Scripting

Affects SolidInvoiceSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 11:07 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: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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.4.0 5 affected builds	Fixed in–

AI-suggested

Given the absence of official patches, European organizations should immediately implement the following mitigations: 1) Apply strict input validation and output encoding on the 'Name' parameter within the Clients Module, either by customizing the application code or using web application firewalls (WAFs) with rules targeting this specific XSS pattern. 2) Restrict access to the /clients endpoint to trusted internal networks or VPNs to reduce exposure to remote attackers. 3) Educate users about phishing and social engineering risks to minimize the chance of user interaction triggering the exploit. 4) Monitor web server and application logs for suspicious input patterns or anomalous requests targeting the vulnerable parameter. 5) Consider deploying Content Security Policy (CSP) headers to limit the execution of injected scripts. 6) Plan for an upgrade or migration to a patched or alternative invoicing solution once available, as reliance on unpatched software increases risk. 7) Regularly back up invoicing data and verify integrity to enable recovery in case of compromise.

Description

A security flaw has been discovered in SolidInvoice up to 2.4.0. The impacted element is an unknown function of the file /clients of the component Clients Module. Performing manipulation of the argument Name results in cross site scripting. The attack is possible to be carried out remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using SolidInvoice up to version 2.4.0, this vulnerability poses a tangible risk to client data confidentiality and user session integrity. Since SolidInvoice is an invoicing and billing platform, exploitation could lead to unauthorized access to sensitive financial information, client details, and potentially manipulation of billing data. This could result in financial fraud, reputational damage, and regulatory non-compliance, especially under GDPR requirements for protecting personal data. The remote exploitability without authentication means attackers can target exposed SolidInvoice instances over the internet, increasing the attack surface. The requirement for user interaction suggests phishing or social engineering could be used to trigger the attack, which is a common vector in European cybercrime campaigns. The lack of vendor response and patches means organizations must rely on their own mitigations, increasing operational risk. The medium severity rating reflects moderate impact but ease of exploitation, making it a relevant threat for European SMEs and enterprises using this software.

Summary

CVE-2025-9171 is a cross-site scripting (XSS) vulnerability identified in SolidInvoice versions up to 2.4.0, specifically within the Clients Module at the /clients endpoint. The vulnerability arises from improper sanitization or validation of the 'Name' argument, allowing an attacker to inject malicious scripts. This flaw can be exploited remotely without authentication, requiring only user interaction to trigger the payload. The vulnerability has a CVSS 4.0 base score of 5.1, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:L), but user interaction is necessary (UI:P). The impact primarily affects the integrity and limited confidentiality of the affected system, as the XSS can be used to hijack user sessions, steal cookies, or perform actions on behalf of the victim user. The vendor has not responded to disclosure attempts, and no official patches or mitigations have been released, increasing the risk for organizations using affected versions. Although no known exploits are currently in the wild, the public availability of the exploit code raises the likelihood of exploitation in the near future.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats