Woo HooWordPress extension · Axiomthemes
CVE-2025-58706
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in axiomthemes Woo Hoo woohoo allows PHP Local File Inclusion.This issue affects Woo Hoo: from n/a through <= 1.25.
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 confidenceLocal File Inclusion (LFI) vulnerability in the Woo Hoo WordPress plugin allows attackers to include arbitrary PHP files from the server by manipulating filename parameters in include/require statements. This occurs due to improper input validation, potentially enabling code execution or disclosure of sensitive files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Woo HooWordPress extension
<= 1.25CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Woo Hoo plugin is installedCheck your WordPress plugins directory (wp-content/plugins/) for a folder named 'woo-hoo' or similar. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to list all installed plugins.Affected if The Woo Hoo plugin by axiomthemes appears in your installed plugins list
-
Check installed version numberIn WordPress admin, go to Plugins > Installed Plugins and locate the Woo Hoo plugin. The version number is displayed beneath the plugin name. If using CLI, inspect the plugin's main PHP file for a 'Version' header comment or check the plugin's readme.txt file.Affected if The displayed version is 1.25 or any version lower than 1.25
-
Confirm plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and check if Woo Hoo shows an 'Activate' or 'Deactivate' link. An active plugin shows 'Deactivate' and has a active status indicator.Affected if The Woo Hoo plugin is currently active (enabled) on the site
-
Identify vulnerable code entry pointReview the plugin files (typically in wp-content/plugins/woo-hoo/) for PHP include/require statements that use unsanitized variables in the path, such as include($_GET['file']) or require($path . $_POST['filename']). Search for patterns like include(, require(, include_once(, require_once( combined with direct use of $_REQUEST, $_GET, or $_POST superglobals.Affected if The plugin contains include/require statements that directly use user-supplied input without proper validation or sanitization
Your environment is affected if the axiomthemes Woo Hoo plugin version 1.25 or lower is installed and active on your WordPress site.
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 dataImplement strict whitelist-based input validation on file inclusion parameters to ensure only allowed files can be included, and update to a patched version of the plugin when available.
Fix this in Woo Hoo
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58706 — 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-2025-58706 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