dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25364

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing 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.8.

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 confidence

This is a Missing Authorization vulnerability in the BoldGrid Client Invoicing (Sprout Invoices) WordPress plugin. The flaw allows attackers to bypass access control security levels due to missing or incorrect authorization checks on certain functionality, potentially exposing sensitive client invoicing data or actions to unauthorized users.

MitigationImplement proper capability checks and authorization verification on all sensitive plugin functions and endpoints. Update to a patched version if available, or audit the code for all locations where access control is enforced and add appropriate WordPress capability checks (e.g., current_user_can()).

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin is installed
    Navigate to WordPress admin > Plugins and look for 'BoldGrid Client Invoicing' or 'Sprout Invoicing' in the installed plugins list
    Affected if The plugin is installed and active - further authorization checks become relevant
  2. Identify installed version
    In WordPress admin > Plugins, click on the plugin name to view details, or check the plugin header in /wp-content/plugins/ directory for the Version field
    Affected if No specific version range is provided in this CVE; compare your version to the patched version once published
  3. Locate plugin entry points
    Inspect the plugin directory structure at /wp-content/plugins/ (plugin folder name may vary - look for boldgrid, sprout-invoices, or similar), identify PHP files handling invoicing functions, AJAX endpoints, or admin pages
    Affected if The plugin is present - these files may contain the vulnerable endpoints lacking authorization checks
  4. Audit for capability checks
    Search plugin PHP files for 'current_user_can' or 'wp_get_current_user' calls within invoicing-related functions. Manually review code around sensitive operations like creating, editing, viewing, or deleting invoices and client data
    Affected if Sensitive functions lack WordPress capability checks (e.g., current_user_can('manage_options') or similar) - this indicates the vulnerability is present
  5. Test endpoint access
    If you have access to multiple user roles (administrator, editor, subscriber, etc.), attempt to access invoicing functions from a low-privilege user account. Check if unauthorized users can view or modify invoicing data they should not access
    Affected if Lower-privileged users can access or perform actions on invoicing data that should require higher privileges

Your environment is affected if the BoldGrid Client Invoicing/Sprout Invoices plugin is active AND sensitive invoicing functions lack proper WordPress capability checks, allowing unauthorized access to client data or actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper capability checks and authorization verification on all sensitive plugin functions and endpoints. Update to a patched version if available, or audit the code for all locations where access control is enforced and add appropriate WordPress capability checks (e.g., current_user_can()).

Recommended fix Moderate confidence

Update to the latest available version of Sprout Invoices (Client Invoicing by Sprout Invoices) - version 20.8.9 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Client Invoicing by Sprout Invoices' (Sprout Invoices)
  4. Check if an update is available for the plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. After updating, verify the plugin version in the plugins list to confirm the update was successful
  7. Test that the plugin functionality works correctly, particularly around access control and invoicing features

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25364 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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