LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32401: WordPress Client Invoicing by Sprout Invoices plugin <= 20.8.9 - Local File Inclusion vulnerability

Improper 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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-32401 affects the WordPress Client Invoicing by Sprout Invoices plugin through version 20.8.9. The flaw can let a highly privileged authenticated user trigger local file inclusion, potentially exposing or affecting sensitive server-side content. It is high severity, but the available sources do not show public exploitation or a named fixed version.

Executive priority

Treat as a priority for WordPress environments using this invoicing plugin. The issue has high potential impact, but current public evidence suggests it requires high privileges and lacks confirmed active exploitation.

Technical view

The CVE describes improper control of filenames in PHP include/require handling, mapped to CWE-98, resulting in PHP local file inclusion. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

WordPress sites are potentially exposed if they run Client Invoicing by Sprout Invoices / sprout-invoices version 20.8.9 or earlier.

Exploitation context

The source bundle marks KEV as false, and no cited source states active exploitation. The CVSS vector indicates exploitation requires high privileges, reducing mass exploitation likelihood but increasing insider or compromised-admin risk.

Researcher notes

Evidence is limited to the CVE record and Patchstack database entry. The bundle does not provide vulnerable code paths, proof-of-concept details, exploit status, or a confirmed patched release. The wording references RFI classification while describing LFI impact.

Mitigation direction

  • Inventory WordPress sites for the sprout-invoices plugin.
  • Identify installations running version 20.8.9 or earlier.
  • Check BoldGrid, WordPress plugin, and Patchstack guidance for a fixed version or vendor mitigation.
  • Restrict high-privilege WordPress accounts to trusted users only.
  • Disable the plugin where business operations do not require it.

Validation and detection

  • Confirm plugin name and version in each WordPress environment.
  • Review administrative account access for unnecessary high-privilege users.
  • Check vendor and Patchstack advisories for updated remediation details.
  • Monitor WordPress and web server logs for unusual privileged activity.
  • Document affected sites and remediation status for tracking.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32401 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-32401Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BoldGridClient Invoicing by Sprout Invoicessprout-invoices, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.