Stored script execution via tax-rate name
Published Aug 19, 2025 · Updated Aug 20, 2025
Stored cross-site scripting in SolidInvoice 2.4.0 and earlier allows remote authenticated users to inject script through a tax-rate name. The /tax/rates workflow stores the untrusted Name value and later renders it without neutralizing executable browser content. A low-privileged account can plant the payload, but execution requires another user to view the affected tax-rates content; impact is limited to actions and data available in that user's browser session.
Summary
What happened
Stored cross-site scripting in SolidInvoice 2.4.0 and earlier allows remote authenticated users to inject script through a tax-rate name. The /tax/rates workflow stores the untrusted Name value and later renders it without neutralizing executable browser content. A low-privileged account can plant the payload, but execution requires another user to view the affected tax-rates content; impact is limited to actions and data available in that user's browser session.
The record
- CVE
- CVE-2025-9170
- Published
- Aug 19, 2025
- Updated
- Aug 20, 2025
- Vendor
- SolidInvoice
- Product
- SolidInvoice
- Classifications
- CWE-79, CWE-94, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- Aug 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0
- Affected versionversion=2.1
- Affected versionversion=2.2
- Affected versionversion=2.3
- Affected versionversion=2.4.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PoC - Stored XSS 4proof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo