CVE-2026-32401
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in BoldGrid Client Invoicing by Sprout Invoices sprout-invoices allows PHP Local File Inclusion.This issue affects Client Invoicing by Sprout Invoices: from n/a through <= 20.8.9.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceLocal File Inclusion (LFI) vulnerability in BoldGrid Client Invoicing by Sprout Invoices WordPress plugin (sprout-invoices) allows attackers to include arbitrary local PHP files due to improper validation of user-supplied input in include/require statements. Successful exploitation can lead to arbitrary code execution if attackers can control or place malicious PHP files on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Sprout Invoices plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'BoldGrid Client Invoicing by Sprout Invoices' or 'sprout-invoices'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'sprout-invoices' or 'sprout-invoices-premium'.Affected if The plugin folder exists in the WordPress plugins directory.
-
Determine the installed plugin versionIn WordPress admin, click on the plugin from the Plugins list and view the version displayed. Alternatively, open the main plugin file (usually sprout-invoices.php or similar) in the plugin folder and look for the 'Version' header in the plugin comment block.Affected if The installed version is any vulnerable release prior to the patched version.
-
Check for vulnerable file inclusion patternsSearch the plugin directory for include/require statements that use variables without proper sanitization. Look for patterns like 'include($_GET[...])', 'require($file)', 'include_once($_REQUEST[...])', or similar dynamic file inclusions. Use grep or a file search tool to scan PHP files in the plugin folder.Affected if Dynamic include/require statements using user-supplied input (GET, POST, REQUEST parameters) are found without sanitization.
-
Identify accessible parameters that control file inclusionReview the plugin's PHP files for parameters that could be controlled by an attacker to specify which file to include. Check for query string parameters or form inputs that feed into the include/require logic found in the previous step.Affected if User-accessible parameters (via URL or form) can influence the file path in include/require statements.
-
Verify if malicious PHP files could be placed on the serverCheck file upload functionality within the plugin or WordPress. Look for any upload handlers that accept PHP files, or check if the web server document root is writable by the attacker.Affected if Attackers can upload PHP files or already have write access to upload directories.
If the sprout-invoices plugin is installed, any version with vulnerable include/require logic that accepts user input is affected, especially if the file inclusion endpoints are accessible and PHP files can be placed on the server.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the sprout-invoices plugin to the latest patched version. If no patched version is available, disable the plugin. Apply input validation using whitelist approaches for any file inclusion logic and ensure strict directory access controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32401 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data