IntegroWordPress extension · Ancorathemes
CVE-2025-58895
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 Integro integro allows PHP Local File Inclusion.This issue affects Integro: from n/a through <= 1.8.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 confidenceLocal File Inclusion vulnerability in AncoraThemes Integro theme (versions through 1.8.0) allows attackers to manipulate file paths in PHP include/require statements, potentially enabling arbitrary code execution or unauthorized access to sensitive server 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
IntegroWordPress extension
<= 1.8.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.
-
Identify the installed Integro theme versionLocate the theme's version declaration. This is typically found in the theme's style.css header (style tag), in a version.php file, or in the theme's main index.php file. Check the theme directory (commonly wp-content/themes/integro/ or similar).Affected if The installed version is 1.8.0 or any earlier version (e.g., 1.7.x, 1.6.0, etc.)
-
Locate PHP files containing include or require statementsSearch the theme directory for PHP files using include, include_once, require, or require_once functions. Examine files that construct file paths dynamically, particularly where user-supplied parameters might influence the included file path.Affected if The theme contains PHP files that use include/require with variable or dynamic file paths without strict validation.
-
Identify parameters that control file inclusionReview the identified include/require files for any parameters (from $_GET, $_POST, $_REQUEST, or configuration values) used directly in the file path. Look for patterns like include($_GET['page']) or require($config['template']).Affected if Any GET, POST, or REQUEST parameters are used directly in include/require statements without sanitization.
-
Check for web-accessible file inclusion entry pointsExamine the theme's PHP files for functions or code that maps URL parameters to file inclusion operations. Look for routes that accept file paths as parameters and pass them to include/require functions.Affected if URL parameters can be manipulated to include arbitrary files from the server filesystem.
-
Review server access logs for suspicious include/require patternsExamine web server access logs (Apache/nginx) for requests containing patterns like ?file=, ?path=, ?page=, ?template= with path traversal sequences (../) or sensitive file paths (e.g., /etc/passwd, config files).Affected if Log entries show attempts to manipulate file inclusion parameters, indicating the vulnerability may be present and actively targeted.
You are affected if the Integro theme version is 1.8.0 or earlier AND the codebase contains include/require statements that use unsanitized user input to construct file paths.
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 input validation and whitelist-based filtering for all file inclusion paths; upgrade to a patched version when released.
Fix this in Integro
Scoped from the published advisory
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58895 — 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-58895 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