CVE-2026-39562
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 · uneditedMissing Authorization vulnerability in BoldGrid Client Invoicing by Sprout Invoices sprout-invoices allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Client Invoicing by Sprout Invoices: from n/a through <= 20.8.10.
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 confidenceMissing authorization vulnerability in BoldGrid Client Invoicing by Sprout Invoices (sprout-invoices) plugin allows attackers to exploit incorrectly configured access control security levels. Users can likely access functionality or data they should not have permission to view or modify due to missing or improper authorization checks in the plugin.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Verify the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and search for 'BoldGrid Client Invoicing' or 'Sprout Invoicing' or 'Sprout Invoices'. Alternatively, check the /wp-content/plugins/ directory for folders containing 'sprout-invoices' or 'boldgrid' in the name.Affected if The plugin appears in the list of installed WordPress plugins
-
Determine the installed versionIn WordPress admin, go to Plugins > Installed Plugins and look at the version number displayed next to the BoldGrid Client Invoicing / Sprout Invoices plugin. Or inspect the main plugin file header in /wp-content/plugins/[plugin-folder]/sprout-invoices.php for the 'Version' comment.Affected if The installed version is any version of the BoldGrid Client Invoicing or Sprout Invoices plugin, since the CVE describes a missing authorization flaw affecting the plugin generally (no specific safe version range was provided)
-
Identify accessible AJAX endpointsCheck the plugin source code in /wp-content/plugins/[plugin-folder]/ for AJAX action registrations (search for 'add_action' with 'wp_ajax_' or 'wp_ajax_nopriv_'). Look at which endpoints are registered without capability checks using current_user_can() or nonce validation.Affected if AJAX endpoints are registered that handle sensitive invoicing functions (such as creating, reading, updating, or deleting invoices, clients, or payments) without requiring user capability verification or nonce validation
You are affected if the BoldGrid Client Invoicing / Sprout Invoices plugin is installed and sensitive AJAX endpoints or functions lack proper capability checks, allowing unauthorized access to invoicing data or actions.
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 to the latest version of the plugin if a patched release is available; otherwise, disable the plugin until a fix is released. If immediate remediation is required, conduct a code review to identify and add proper capability checks and nonce validations to all sensitive functions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39562 — 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-39562 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