TakeoutWordPress extension · Ancorathemes
CVE-2025-58901
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 AncoraThemes Takeout takeout allows PHP Local File Inclusion.This issue affects Takeout: from n/a through <= 1.3.0.
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 AncoraThemes Takeout WordPress theme (versions <= 1.3.0) contains a PHP Local File Inclusion (LFI) vulnerability where the application does not properly validate or sanitize user-supplied input used in include/require statements. This allows an attacker to potentially include arbitrary local PHP files, leading to information disclosure or code execution.
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
TakeoutWordPress extension
<= 1.3.0CVSS 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.
-
Confirm Takeout plugin/theme installationLocate the AncoraThemes Takeout installation in your web root or CMS plugin directory. Check for a version file, header comment in the main PHP file, or use your CMS admin panel to view the installed version.Affected if AncoraThemes Takeout version 1.3.0 or lower is installed.
-
Verify installed versionOpen the main Takeout file (often named takeout.php, index.php, or similar in the plugin/theme directory) and locate the version declaration in the file header comments or a dedicated version constant.Affected if The version string shows 1.3.0 or any version lower than 1.3.0.
-
Identify file inclusion codeSearch the Takeout source files for PHP include, include_once, require, or require_once statements. Look for patterns where a variable is passed to these functions, such as include($file), include($_GET['page']), or require($path).Affected if File inclusion code exists that uses dynamic variables without sanitization.
-
Inspect input sourceExamine the PHP files found in the previous step to determine if the variable used in the include/require statement receives its value from user input sources such as $_GET, $_POST, $_REQUEST, or URL parameters.Affected if User-supplied input from GET, POST, or REQUEST parameters flows directly into include/require statements.
-
Check input validationReview the code around the file inclusion to see if any validation exists before the include/require call. Look for functions like basename(), realpath(), preg_match(), or allowlist checks. Also verify whether directory traversal sequences (..) are being filtered.Affected if No input validation, sanitization, or allowlist checking is performed before the file inclusion, or traversal sequences are not blocked.
You are affected if AncoraThemes Takeout version 1.3.0 or lower is installed and the vulnerable file inclusion parameters accept unsanitized user input that can be manipulated to read arbitrary files.
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 the patched version of Takeout if available. If no patch exists, implement strict input validation using an allowlist approach on all include/require parameters, disable allow_url_include in PHP configuration, and consider setting open_basedir restrictions.
Fix this in Takeout
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58901 — 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-58901 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