777WordPress extension · Axiomthemes
CVE-2025-58708
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 777 triple-seven allows PHP Local File Inclusion.This issue affects 777: from n/a through <= 1.3.
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 confidenceA PHP File Inclusion vulnerability in the axiomthemes 777 triple-seven theme (version 1.3 and below) allows attackers to manipulate include/require statements to execute arbitrary PHP code via local file inclusion (LFI), potentially leading to full system compromise.
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
777WordPress extension
<= 1.3CVSS 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 installed theme versionLocate the theme's style.css file and check the 'Version:' header in the theme comments at the top, or check the theme's main functions.php file for a version definitionAffected if The reported version is 1.3 or any version lower than 1.3 (e.g., 1.2, 1.1, 1.0)
-
Find PHP file inclusion functionsSearch all .php files within the theme directory for usage of include, include_once, require, or require_once statements that accept variable inputAffected if The theme contains include/require statements using variables from $_GET, $_POST, or $_REQUEST without sanitization
-
Inspect parameter handlingExamine the identified inclusion code to determine whether URL parameters (such as 'page', 'file', 'path', 'template', or similar) are passed directly to include/require functionsAffected if User-supplied parameters are used in file inclusion functions without validation or whitelist filtering
-
Verify file inclusion is reachableConfirm that the vulnerable inclusion code is accessible via HTTP requests (not restricted by authentication or conditional logic that prevents normal access)Affected if The file inclusion code executes based on standard GET or POST requests without requiring admin authentication
-
Check for input validationReview the code surrounding the inclusion statements to determine if there is any input validation, sanitization, or whitelist-based filtering applied to the parameter before the include/require callAffected if There is no input validation or the validation can be bypassed, allowing arbitrary file paths to be supplied
You are affected if the installed theme version is 1.3 or below AND your deployment uses file inclusion 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 dataUpgrade to a patched version of the theme; implement strict input validation and whitelist-based filtering on all file inclusion parameters; disable allow_url_fopen and allow_url_include in PHP configuration.
Fix this in 777
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58708 — 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-58708 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