dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-48117

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-16
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 kilbot WooCommerce POS woocommerce-pos allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooCommerce POS: from n/a through <= 1.7.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

A missing authorization vulnerability in the WooCommerce POS plugin allows unauthenticated or unauthorized attackers to access sensitive functionality or data due to incorrectly configured access control security levels. The vulnerability exists in versions through 1.7.8, where proper authorization checks are not enforced on certain endpoints or actions.

MitigationUpdate WooCommerce POS to the latest version beyond 1.7.8 when available. If no patch exists, implement proper authorization checks on all sensitive endpoints and functions, and restrict access based on user roles and capabilities.

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. Identify WooCommerce POS version
    In WordPress admin, go to Plugins > Installed Plugins, find WooCommerce POS, and note the version number displayed. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if The installed version is 1.7.8 or lower (any version 'through 1.7.8' is affected)
  2. Locate POS plugin files
    Navigate to wp-content/plugins/woocommerce-pos/ in your WordPress installation directory and list the main plugin files.
    Affected if The plugin directory exists and contains the WooCommerce POS plugin files
  3. Check for POS REST API endpoints
    Access your site's WP-JSON endpoint and look for /wp-json/pos/ or similar POS-related routes. Visit URLs like: yoursite.com/wp-json/pos/v1/ and yoursite.com/wp-json/wc/v3/pos/ to see if endpoints respond without authentication.
    Affected if POS endpoints respond to unauthenticated or low-privilege user requests
  4. Inspect POS capability requirements
    Open the main plugin PHP files and search for 'capability', 'manage_options', or 'author' to see what user roles are required for POS actions.
    Affected if No capability checks or overly permissive capability requirements are found for sensitive POS functions

Your environment is affected if WooCommerce POS version 1.7.8 or lower is installed and POS endpoints or functions are accessible without proper authorization verification.

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 WooCommerce POS to the latest version beyond 1.7.8 when available. If no patch exists, implement proper authorization checks on all sensitive endpoints and functions, and restrict access based on user roles and capabilities.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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