dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-6510

CRITICAL · 9.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 →
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 InfusedWoo Pro plugin for WordPress is vulnerable to privilege escalation via missing authorization in all versions up to, and including, 5.1.2. This is due to missing nonce verification and capability checks in the iwar_save_recipe() AJAX handler. This makes it possible for unauthenticated attackers to create a malicious automation recipe that pairs an HTTP post trigger with an auto-login action, allowing any unauthenticated visitor to visit a crafted URL and receive authentication cookies for any targeted user account (e.g., administrator), achieving complete authentication bypass and privilege escalation.

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 WordPress plugin versions up to 5.1.2 contain a critical authentication bypass in the iwar_save_recipe() AJAX handler. The function lacks both nonce verification and capability checks, allowing unauthenticated attackers to craft malicious automation recipes that pair HTTP post triggers with auto-login actions. This enables any visitor to obtain valid authentication cookies for arbitrary user accounts (including administrators), achieving full privilege escalation.

MitigationUpgrade to version 5.1.3 or later, which should include proper nonce verification and capability checks in the AJAX handler. Until patched, consider disabling the plugin or restricting access to the vulnerable AJAX endpoint.

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. Locate the InfusedWoo Pro plugin
    Check your WordPress installation under wp-content/plugins/ for a folder named 'infusedwoo-pro' or search for 'infusedwoo' in the plugin directory.
    Affected if The plugin folder exists in your WordPress plugins directory.
  2. Identify the installed version
    Open the main plugin PHP file (often infusedwoo-pro.php or similar) and look for the version comment in the file header, or check the plugin's readme.txt for the 'Stable tag' version number.
    Affected if The version is 5.1.2 or lower (the plugin is vulnerable up to and including version 5.1.2).
  3. Verify the AJAX handler is registered
    Search the plugin source code for 'iwar_save_recipe' to confirm this AJAX function exists. Check if it is hooked to wp_ajax_nopriv_ or wp_ajax_ actions (the presence of wp_ajax_nopriv_iwar_save_recipe means it's accessible to unauthenticated users).
    Affected if The function iwar_save_recipe is hooked to wp_ajax_nopriv_ (making it publicly accessible without login) without nonce verification in the handler.
  4. Confirm lack of capability checks
    Review the iwar_save_recipe function code to verify it does NOT call current_user_can() or a similar capability check before processing the recipe data.
    Affected if The AJAX handler contains no capability verification (no current_user_can() or similar check) and no nonce verification.

You are affected if InfusedWoo Pro plugin is installed with version 5.1.2 or lower and the iwar_save_recipe AJAX handler is exposed without authentication and capability checks.

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

Upgrade to version 5.1.3 or later, which should include proper nonce verification and capability checks in the AJAX handler. Until patched, consider disabling the plugin or restricting access to the vulnerable AJAX endpoint.

Recommended fix Moderate confidence

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

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate InfusedWoo Pro in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running on version 5.1.3 or later
  6. 6. Review any recently created automation recipes in the InfusedWoo settings and delete any suspicious recipes you did not create
  7. 7. Consider forcing password reset for administrator accounts as a precautionary measure
Caveat Review plugin settings after upgrade as minor configuration changes may occur

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing5.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,630
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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