FrameWordPress extension · Ancorathemes
CVE-2025-58899
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 Frame frame allows PHP Local File Inclusion.This issue affects Frame: from n/a through <= 2.4.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 (LFI) vulnerability in AncoraThemes Frame theme <= 2.4.0 allows attackers to include arbitrary local files via improper control of filename parameters in PHP include/require statements. This can enable unauthorized reading of sensitive server files such as configuration files, credentials, or system 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
FrameWordPress extension
<= 2.4.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.
-
Locate the installed Frame theme versionCheck the theme's style.css file (usually in /wp-content/themes/frame/) for the 'Version:' header, or look for a version constant in functions.php or theme.jsonAffected if The version listed is 2.4.0 or lower
-
Identify PHP files with dynamic include/require statementsSearch theme files (particularly in the root and includes/ folders) for patterns like 'include($_GET[', 'require($_POST[', 'include($' followed by any variable that could be user-controlledAffected if Dynamic include/require statements using variables that could be influenced by user input exist in accessible PHP files
-
Determine web accessibility of vulnerable includesCheck if the identified PHP files containing dynamic includes/requires are directly accessible via HTTP (not blocked by .htaccess or WordPress routing)Affected if The PHP files with dynamic includes are reachable via web requests without authentication
-
Inspect PHP configuration for dangerous settingsCheck phpinfo() or php.ini for allow_url_include = 1 (allows remote file inclusion, amplifying LFI impact)Affected if allow_url_include is enabled, increasing the severity of any LFI vulnerability
-
Review web server logs for LFI exploitation attemptsSearch access logs for patterns like '../', '..\', '/etc/passwd', 'wp-config.php' in URL parameters, especially targeting theme PHP filesAffected if Recent or historical requests contain path traversal patterns targeting theme files
You are affected if the Frame theme version is 2.4.0 or lower AND PHP files using dynamic include/require with user-controlled parameters are web-accessible.
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 dataUpgrade to the latest version of the Frame theme which contains proper input validation on include/require statements. If no update is available, implement strict whitelist-based validation on all user-controlled file path parameters and disable allow_url_include in PHP configuration.
Fix this in Frame
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58899 — 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-58899 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