dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-4880

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The Barcode Scanner (+Mobile App) – Inventory manager, Order fulfillment system, POS (Point of Sale) plugin for WordPress is vulnerable to privilege escalation via insecure token-based authentication in all versions up to, and including, 1.11.0. This is due to the plugin trusting a user-supplied Base64-encoded user ID in the token parameter to identify users, leaking valid authentication tokens through the 'barcodeScannerConfigs' action, and lacking meta-key restrictions on the 'setUserMeta' action. This makes it possible for unauthenticated attackers to escalate their privileges to that of an administrator by first spoofing the admin user ID to leak their authentication token, then using that token to update any user's 'wp_capabilities' meta to gain full administrative access.

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 · high confidence

The WordPress plugin uses Base64-encoded user-supplied user IDs to identify users in token-based authentication, allowing unauthenticated attackers to leak admin authentication tokens via the barcodeScannerConfigs action and then escalate privileges by modifying wp_capabilities meta through the unrestricted setUserMeta action.

MitigationUpdate the plugin to version 1.11.1 or later when available; until then, disable the plugin or restrict access to vulnerable AJAX actions at the server level.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify the vulnerable plugin
    List all WordPress plugins and compare their names against known vulnerable plugin names for CVE-2026-4880; check plugin directory for the plugin associated with barcode scanner functionality
    Affected if The plugin associated with CVE-2026-4880 is installed and active
  2. Check plugin version
    Access the plugin file header (typically in main plugin PHP file) or view plugin details in WordPress admin under Plugins > Installed Plugins, then compare the version to the fixed version 1.11.1
    Affected if Plugin version is lower than 1.11.1 or the version cannot be determined
  3. Verify AJAX action exposure
    Inspect the plugin PHP code for registered AJAX actions named barcodeScannerConfigs and setUserMeta using wp_ajax_ hooks (e.g., add_action('wp_ajax_barcodeScannerConfigs', ...)); attempt a direct HTTP request to /wp-admin/admin-ajax.php?action=barcodeScannerConfigs to confirm the endpoint responds
    Affected if Both barcodeScannerConfigs and setUserMeta AJAX actions are registered and accessible without authentication
  4. Check token-based authentication configuration
    Search plugin code for Base64 encoding usage in authentication logic (e.g., base64_decode() applied to user-supplied input); inspect if token-based auth is actively enabled in plugin settings
    Affected if Base64-encoded user IDs are used in token-based authentication and the feature is enabled
  5. Confirm WordPress meta capability access
    Review the setUserMeta action implementation to verify it allows direct modification of wp_capabilities user meta without capability checks; check if any user can trigger this action
    Affected if The setUserMeta action permits modification of wp_capabilities meta without proper authorization checks

A user is affected if the vulnerable WordPress plugin (with barcode scanner functionality) is installed with version lower than 1.11.1 and the barcodeScannerConfigs/setUserMeta AJAX actions are exposed without authentication.

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 the plugin to version 1.11.1 or later when available; until then, disable the plugin or restrict access to vulnerable AJAX actions at the server level.

Recommended fix Moderate confidence

Version 1.11.1 or later (check WordPress plugin repository for latest release)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the 'Barcode Scanner (+Mobile App) – Inventory manager, Order fulfillment system, POS (Point of Sale)' plugin
  3. 3. Check the current installed version - if it is 1.11.0 or below, an update is needed
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is functioning correctly by testing the barcode scanning functionality
  6. 6. Confirm that unauthorized users can no longer access admin functions through the vulnerable token mechanism

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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