FestyWordPress extension · Ancorathemes
CVE-2025-58879
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 Festy festy allows PHP Local File Inclusion.This issue affects Festy: from n/a through <= 1.13.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 · high confidenceThe Festy theme from AncoraThemes contains a PHP file inclusion vulnerability (CWE-98) where user-controlled input is used in include/require statements without proper validation. Attackers can exploit this to include arbitrary local (or potentially remote) PHP files, leading to remote code execution. The vulnerability exists in versions up to and including 1.13.0.
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
FestyWordPress extension
<= 1.13.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 Festy theme installationCheck your web server's theme directory, typically at wp-content/themes/festy/ or similar path depending on your WordPress installation structure.Affected if The Festy theme directory exists on the server.
-
Determine Festy theme versionOpen the style.css file in the theme directory and look for the version comment in the file header, or check theme.json if present.Affected if The version listed is 1.13.0 or lower, or no version is declared.
-
Identify PHP files with dynamic includesSearch all .php files within the Festy theme directory for include, require, include_once, or require_once statements that reference variables such as $_GET, $_POST, or $_REQUEST.Affected if Any PHP file contains include/require statements using unsanitized user-supplied input as the path.
-
Inspect file inclusion parameter handlingExamine the identified include statements to determine if the user input goes through path traversal sequences or is used directly without validation using functions like basename() or whitelist filtering.Affected if The include statement accepts user input without sanitization or uses path traversal characters (..) without restriction.
-
Verify PHP configuration settingsCheck the php.ini or runtime configuration for allow_url_include setting.Affected if allow_url_include is enabled, allowing remote file inclusion in addition to local.
You are affected if the Festy theme version is 1.13.0 or lower AND any PHP file within the theme uses include/require with unsanitized user input from request parameters.
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 using whitelist-based filtering for file inclusion parameters, apply basename() to strip path traversal sequences, disable allow_url_include in PHP configuration, and ensure all include statements use hardcoded absolute paths rather than user-supplied values.
Fix this in Festy
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58879 — 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-58879 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