ConvexWordPress extension · Axiomthemes
CVE-2025-53449
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 Convex convex allows PHP Local File Inclusion.This issue affects Convex: from n/a through <= 1.11.
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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Convex theme from axiomthemes. The vulnerability allows attackers to manipulate file inclusion functions to include arbitrary PHP files from the local server, potentially leading to remote code execution.
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
ConvexWordPress extension
<= 1.11CVSS 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 if Convex theme is installedLocate theme files in the wp-content/themes/ directory and check for a folder named 'convex' or 'Convex'. Look for theme definition files like style.css or theme.json that contain the theme name.Affected if The Convex theme by axiomthemes is present in the themes directory.
-
Check the Convex theme versionOpen the theme's style.css file (typically in wp-content/themes/convex/) and look for the 'Version:' declaration in the file header. Alternatively, check theme.json for a version field.Affected if The reported version is 1.11 or lower.
-
Identify PHP include/require usage in theme filesSearch theme PHP files for include, require, include_once, or require_once statements that use variables (e.g., include($var), require($_GET['file']) ). Focus on files in the theme's root directory and any 'inc' or 'includes' subfolders.Affected if Dynamic file inclusion using user-controlled parameters (GET, POST, or COOKIE variables) is present.
-
Inspect the vulnerable file inclusion parametersExamine identified dynamic include/require statements. Check if they accept file paths from request parameters (commonly 'file', 'template', 'path', 'page', or 'include' parameters) without strict sanitization.Affected if File inclusion functions accept unsanitized user input and the parameters are directly accessible via HTTP requests.
-
Verify PHP configuration relevant to LFI impactCheck php.ini for allow_url_fopen setting. While this is an LFI (local file inclusion), assess if the server configuration allows reading sensitive files that could be included.Affected if allow_url_fopen is enabled or the web server process has read access to sensitive system files.
You are affected if the Convex theme version is 1.11 or lower AND dynamic file inclusion using unsanitized user input exists in the theme's PHP code.
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 file inclusion logic. Disable allow_url_fopen and ensure all user-supplied parameters used in include/require statements are sanitized and validated against an allowlist of permitted files.
Fix this in Convex
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53449 — 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-53449 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