ParagonWordPress extension · Axiomthemes
CVE-2025-58225
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 Paragon paragon allows PHP Local File Inclusion.This issue affects Paragon: from n/a through <= 1.1.
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 Paragon theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability that allows attackers to include arbitrary files from the server file system. This occurs due to improper control of filename parameters in include/require statements, potentially enabling exposure of sensitive configuration files, credentials, or code execution if attacker-controlled files can be uploaded and included.
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
ParagonWordPress extension
<= 1.1CVSS 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 Paragon theme installationSearch the web server file system for the Paragon theme directory, typically found in wp-content/themes/paragon or similar paths under the web root.Affected if The Paragon theme directory exists on the server
-
Identify installed theme versionOpen the theme style.css file (usually at wp-content/themes/paragon/style.css) and locate the Version header in the comment block at the top.Affected if The version listed is 1.1 or lower, or no version is declared (indicating an unpatched release)
-
Search for vulnerable include/require patternsUse grep or a file search tool to scan PHP files in the Paragon theme directory for include/require statements that use variables without sanitization, such as: include($_GET[...]), include($var), require($_REQUEST[...])Affected if Unsanitized file inclusion calls are found that accept user-controlled input
-
Check for exposed file inclusion parametersReview the theme PHP files for GET/POST/REQUEST parameters passed to include or require statements without validation, then test if these parameters are accessible via HTTP requests.Affected if File inclusion parameters are reachable and accept arbitrary file paths
-
Inspect for sensitive file accessAttempt to include a known safe local file (such as /etc/passwd on Linux or wp-config.php in WordPress installations) using the identified vulnerable parameter to confirm LFI capability.Affected if The server returns contents of files outside the theme directory
A system is affected if the Paragon theme version is 1.1 or lower and the theme contains vulnerable include/require statements that accept unsanitized user input accessible via web requests.
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 a patched version of the Paragon theme; until available, implement strict whitelist-based input validation on all file inclusion parameters and disable allow_url_include in PHP configuration.
Fix this in Paragon
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58225 — 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-58225 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