CVE-2026-6514
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 Arbitrary File Read in all versions up to, and including, 5.1.2 via the popup_submit. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 confidenceThe InfusedWoo Pro WordPress plugin versions up to 5.1.2 contains an unauthenticated Arbitrary File Read vulnerability via the popup_submit parameter. This SSRF-type flaw allows attackers to make arbitrary web requests from the server, potentially enabling access to internal services and sensitive file contents.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm InfusedWoo Pro plugin is installedLocate the InfusedWoo Pro plugin directory within the WordPress plugins folder (typically wp-content/plugins/) or check the WordPress admin plugin list for InfusedWoo ProAffected if The plugin is present in the WordPress installation
-
Identify the installed versionOpen the main InfusedWoo Pro plugin file (usually infusedwoo.php or similar in the plugin directory) and locate the version declaration in the plugin header comment, or check the plugin's readme.txt fileAffected if The version number is 5.1.2 or lower
-
Verify the vulnerable endpoint is accessibleTest access to the endpoint that handles the popup_submit parameter (typically via wp-admin/admin-ajax.php or a front-facing AJAX handler) without providing any authentication credentialsAffected if The endpoint responds to unauthenticated requests containing the popup_submit parameter
-
Check if the plugin is activeVerify the InfusedWoo Pro plugin status in WordPress admin under Plugins > Installed Plugins, or query the WordPress options table for the active_plugins settingAffected if The plugin is currently activated on the WordPress site
The environment is affected if InfusedWoo Pro plugin is installed, active, and running version 5.1.2 or lower with the popup_submit parameter endpoint exposed and accessible without authentication.
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 to a patched version of InfusedWoo Pro beyond 5.1.2 once available, or implement strict input validation and access controls on the popup_submit parameter to restrict requests to allowed origins.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6514 — 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-6514 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