AlgenixWordPress extension · Axiomthemes
CVE-2025-58803
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 Algenix algenix allows PHP Local File Inclusion.This issue affects Algenix: from n/a through <= 1.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 confidenceA PHP Local File Inclusion vulnerability in the Algenix theme by axiomthemes allows attackers to include arbitrary local PHP files through improperly sanitized input in include/require statements. The lack of proper input validation on file path parameters enables directory traversal and arbitrary file inclusion attacks.
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
AlgenixWordPress extension
<= 1.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.
-
Confirm Algenix theme installationLocate the theme directory on the web server. For WordPress, check wp-content/themes/ for a folder named 'algenix' or 'Algenix'. For other platforms, search for files containing 'algenix' in the theme name.Affected if The Algenix theme directory exists on the server.
-
Determine theme versionOpen the theme's style.css file (typically in the theme root directory) and locate the 'Version:' comment header. Alternatively, check theme.json for a 'version' field.Affected if The reported version is 1.0 or lower (e.g., 1.0, 0.9, 0.8).
-
Identify file inclusion codeSearch the theme's PHP files for include, require, include_once, or require_once statements that use variables without validation. Common patterns include: include($_GET['file']), require($path . $_POST['include']), or similar constructions.Affected if File inclusion functions accept user-supplied input (from $_GET, $_POST, $_REQUEST) without sanitization or validation checks.
-
Check for vulnerable parameter handlingExamine PHP files that process file paths, particularly those that concatenate user input with directory paths. Look for code that uses parameters like 'file', 'path', 'template', 'page', or 'include' in request variables without validating they point to allowed files.Affected if Parameters accepting file paths are used directly in inclusion functions without checking for directory traversal patterns (../) or restricting to allowed file extensions.
-
Inspect HTTP traffic and logsReview web server access logs (e.g., access.log, error.log) for requests containing ../ patterns or unusual file paths being passed to theme parameters. Look for requests to PHP files in the theme directory with suspicious path values.Affected if Logs show requests with directory traversal sequences (e.g., ../../wp-config.php) or attempts to include non-theme files through URL parameters.
A system is affected if the Algenix theme version is 1.0 or lower AND the theme contains PHP code that uses user-supplied input in include/require statements without validation.
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 dataAudit and sanitize all include/require statements to use allowlists or validate paths strictly; remove user-controllable input from file inclusion logic or implement basename() filtering to prevent directory traversal.
Fix this in Algenix
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58803 — 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-58803 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