dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-31628

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-01
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 SlicedInvoices Sliced Invoices sliced-invoices allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Sliced Invoices: from n/a through <= 3.10.0.

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

Missing authorization vulnerability in SlicedInvoices WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to certain functionality, potentially enabling unauthorized users to perform actions reserved for higher-privileged roles.

MitigationUpdate SlicedInvoices to the latest patched version. If no update is available, implement role-based access control checks at all sensitive endpoints and audit the plugin's capability verification logic.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify SlicedInvoices plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'SlicedInvoices' in the list of active plugins.
    Affected if The SlicedInvoices plugin is present and active in the WordPress installation.
  2. Check installed plugin version
    In Plugins > Installed Plugins, find SlicedInvoices and note the version number displayed below the plugin name. Compare this version against the vendor's release notes for the patched version.
    Affected if The installed version is older than the latest version containing the security patch.
  3. Inspect WordPress user roles and capabilities
    Navigate to Users > Roles or use a role editor plugin to review capabilities assigned to each role. Look specifically for SlicedInvoices-related capabilities (such as 'manage_sliced_invoices', 'edit_sliced_invoices', or similar) assigned to roles below Administrator.
    Affected if Any role with privilege level lower than Administrator has been granted SlicedInvoices administrative capabilities.
  4. Test access to plugin admin functions with low-privilege user
    Log in with a low-privilege account (e.g., Subscriber or Contributor) and attempt to access SlicedInvoices admin pages directly via URL or navigation menu. Alternatively, use a browser's developer tools to inspect if admin AJAX endpoints or form submissions return successful responses.
    Affected if A user without Administrator role can access SlicedInvoices admin functionality or successfully submit requests that should require elevated privileges.
  5. Review capability checks in plugin code
    If you have file system access, locate the SlicedInvoices plugin directory (wp-content/plugins/sliced-invoices) and search PHP files for 'current_user_can', 'capability', or 'permission' to see if proper authorization checks exist before sensitive operations.
    Affected if Sensitive functions lack proper current_user_can() capability checks or use weak permission validation.

A user is affected if the SlicedInvoices plugin is installed with a vulnerable version AND low-privilege users can access administrative functionality they should not be able to reach.

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

Update SlicedInvoices to the latest patched version. If no update is available, implement role-based access control checks at all sensitive endpoints and audit the plugin's capability verification logic.

Recommended fix Moderate confidence

Latest version of Sliced Invoices plugin (version higher than 3.10.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Sliced Invoices plugin
  4. Check if an update is available for the plugin
  5. If an update is available, update the plugin to the latest version
  6. If no update is available through the WordPress admin, manually download the latest version from the WordPress plugin repository or the vendor's website and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin is functioning correctly
  8. Review user roles and permissions to ensure proper access controls are in place

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31628 — 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-2025-31628 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