Client Invoicing by Sprout Invoices <= 20.8.9 - Authenticated (Author+) Local File Inclusion
Strategic Overview
- Status
- Patched in 20.8.10
- Affected Plugin
- Sprout Invoices – Client Invoicing & Estimates
- Affected Version
<= 20.8.9- CVSS
- 7.5High
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2026-32401
At a glance
CVE-2026-32401 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Sprout Invoices WordPress plugin, affecting versions <= 20.8.9. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 20.8.10; sites on affected versions should update now. Disclosed February 2026, reported by daroo.
Vulnerability Overview
The Client Invoicing by Sprout Invoices plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 20.8.9. This makes it possible for authenticated attackers, with author-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other "safe" file types can be uploaded and included.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Sprout Invoices <= 20.8.9 carries this weakness at safe, and reaching it takes an account at Author level or above. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.
Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For Sprout Invoices the fix is 20.8.10: builds <= 20.8.9 are affected, anything from 20.8.10 onward is not.
Remediation
Update to version 20.8.10, or a newer patched version
How does WordSec protect against this?
An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Sprout Invoices 20.8.10 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in Sprout Invoices – Client Invoicing & Estimates
- 8.1CVE-2025-64227: Client Invoicing by Sprout… PHP Object Injection
CVE-2025-64227 - 7.3Client Invoicing by Sprout Invoices Missing Authorization
- 5.3CVE-2026-39562: Client Invoicing by Sprout… Missing Authorization
CVE-2026-39562 - 5.3CVE-2026-25364: Client Invoicing by Sprout… Missing Authorization
CVE-2026-25364 - 5.3CVE-2024-53819: Client Invoicing by Sprout Invoices <= 20.8.0 IDOR
CVE-2024-53819 - 5.0CVE-2025-24606: Client Invoicing by Sprout… Missing Authorization
CVE-2025-24606 - 4.8CVE-2021-24787: Client Invoicing by Sprout Invoices Stored XSS
CVE-2021-24787 - 4.3CVE-2026-57418: Sprout Invoices Missing Authorization
CVE-2026-57418
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C