dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-49888

HIGH · 7.1 CVSS v3.1 Published 2025-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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 pimwick PW WooCommerce On Sale! pw-woocommerce-on-sale allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PW WooCommerce On Sale!: from n/a through <= 1.39.

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 the pimwick PW WooCommerce On Sale! WordPress plugin allows attackers to exploit incorrectly configured access control security levels. This enables unauthorized users to access sale-related functionality they should not have permission to view or modify.

MitigationUpdate the plugin to the latest patched version once available, and review user role permissions to ensure proper access controls are enforced.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 checks

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

  1. Verify PW WooCommerce On Sale plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PW WooCommerce On Sale!' by pimwick, or check the plugins directory at /wp-content/plugins/ for a folder starting with 'pw-woocommerce-on-sale'
    Affected if The plugin is installed and active
  2. Identify the installed plugin version
    In WordPress admin Plugins page, click on the plugin name to view details and find the version number, or read the main plugin PHP file header for the 'Version' tag
    Affected if Version cannot be determined or is earlier than the patched version
  3. Check for publicly accessible AJAX endpoints
    Inspect the plugin directory for AJAX action handlers (wp_ajax_ and wp_ajax_nopriv_ hooks) in files like class-pw-woocommerce-on-sale.php or similar main plugin files; use a network scanner or check source code for add_action('wp_ajax_...') and add_action('wp_ajax_nopriv_...') calls related to sale functionality
    Affected if AJAX endpoints related to sale data are registered with nopriv capability allowing unauthenticated access
  4. Review sale-related REST API routes
    Check plugin files for REST API route registration using add_action('rest_api_init') and register_rest_route() calls; test by accessing /wp-json/pw-woocommerce-on-sale/v1/ endpoints without authentication
    Affected if REST API routes exposing sale functionality are accessible without authentication or with insufficient capability checks
  5. Verify user role capability assignments
    In WordPress admin under Users > User Role Editor or similar, check if the plugin adds custom capabilities (like 'view_sales', 'edit_sales') and whether these are incorrectly assigned to low-privilege roles or the Subscriber role
    Affected if Users with Subscriber or similar low-privilege roles can access sale-related functionality they should not have permission to view or modify

If the plugin is installed and unauthenticated users can access sale-related functionality through AJAX, REST API, or improper role assignments, the environment is affected by this authorization bypass vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest patched version once available, and review user role permissions to ensure proper access controls are enforced.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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