dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-6506

HIGH · 8.8 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The InfusedWoo Pro plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 5.1.2. This is due to the infusedwoo_gdpr_upddata() function missing authorization and capability checks, as well as lacking restrictions on which user meta keys can be updated. This makes it possible for authenticated attackers, with subscriber-level access and above, to update their own wp_capabilities user meta to grant themselves Administrator role privileges.

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 InfusedWoo Pro plugin for WordPress contains a privilege escalation vulnerability in the infusedwoo_gdpr_upddata() function. This function allows authenticated users with subscriber-level access to update arbitrary user meta keys, including wp_capabilities, enabling them to grant themselves Administrator privileges.

MitigationUpdate InfusedWoo Pro to version 5.1.3 or later which includes proper authorization checks and meta key restrictions. If no patch is available, remove the plugin until a secure version is released.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 if InfusedWoo Pro plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'InfusedWoo Pro' in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation
  2. Check the installed version of InfusedWoo Pro
    In the WordPress admin, go to Plugins > Installed Plugins and locate InfusedWoo Pro. The version number is displayed below the plugin name. Alternatively, check the plugin header in the main plugin file (typically /wp-content/plugins/infusedwoo-pro/infusedwoo.php) for the 'Version' comment.
    Affected if The version number is 5.1.2 or lower
  3. Verify the vulnerable function exists in the codebase
    Access the WordPress site files via FTP or file manager. Locate the main InfusedWoo Pro plugin directory and search for the function 'infusedwoo_gdpr_upddata' within the PHP files.
    Affected if The function infusedwoo_gdpr_upddata exists in the plugin files, indicating the vulnerable code is present
  4. Determine if the GDPR update feature is accessible
    Inspect the plugin code to confirm the infusedwoo_gdpr_upddata function is hooked to an accessible action (such as init, admin_init, or a REST API endpoint) without proper capability checks.
    Affected if The function is hooked to a publicly accessible WordPress action without authorization checks
  5. Audit user accounts for privilege escalation
    In WordPress admin, navigate to Users > All Users. Review the roles assigned to each user, particularly looking for subscriber-level accounts that may have been escalated to Administrator. Check the wp_usermeta table directly for any user with wp_capabilities containing 'administrator' who should not have that role.
    Affected if Any subscriber-level accounts have been granted Administrator privileges or wp_capabilities meta has been modified unexpectedly

If InfusedWoo Pro version 5.1.2 or lower is installed and active, with the infusedwoo_gdpr_upddata function present and accessible, the environment is affected by this privilege escalation 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 InfusedWoo Pro to version 5.1.3 or later which includes proper authorization checks and meta key restrictions. If no patch is available, remove the plugin until a secure version is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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