CVE-2026-6512
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 · uneditedThe InfusedWoo Pro plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.1.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to permanently delete arbitrary posts, pages, products, or orders, mass-delete all comments on any post, and change any post's status.
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 confidenceThe InfusedWoo Pro WordPress plugin fails to perform proper authorization checks on certain AJAX actions and admin requests. This allows unauthenticated attackers to invoke sensitive functions that should require administrative privileges, enabling deletion of arbitrary content (posts, pages, products, orders) and modification of post statuses without any authentication.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm InfusedWoo Pro is installedIn WordPress admin, go to Plugins > Installed Plugins and locate InfusedWoo Pro. Note whether it is active or inactive.Affected if The plugin is installed and active, exposing its AJAX endpoints.
-
Identify installed plugin versionIn the plugins list, click on the plugin name to view details, or inspect the plugin main file header for the Version field. Compare this version number to 5.1.3.Affected if The installed version is lower than 5.1.3, indicating it likely contains the authorization flaw.
-
Inspect AJAX action registrationExamine the plugin directory (wp-content/plugins/infusedwoo) for PHP files containing add_action("wp_ajax_...) calls. Check if any sensitive actions (such as delete_post, update_post_status, or similar content manipulation functions) are registered without a corresponding wp_ajax_nopriv_ hook check for authentication.Affected if Sensitive AJAX actions lack nopriv handlers or do not verify user capabilities before executing.
-
Test AJAX endpoint accessibilitySend a crafted POST request to /wp-admin/admin-ajax.php with action parameter matching a sensitive function (e.g., action=infusedwoo_delete_post) without providing authentication cookies or credentials. Observe whether the request executes successfully.Affected if The AJAX endpoint executes the requested sensitive operation without requiring authentication.
A user is affected if the InfusedWoo Pro plugin is active with a version lower than 5.1.3 and its AJAX endpoints allow unauthenticated content deletion or status modification.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the InfusedWoo Pro plugin to version 5.1.3 or later. Until an update is available, disable the plugin or implement firewall rules to block suspicious requests to the affected AJAX endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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