CerebrumWordPress extension · Axiomthemes
CVE-2025-58926
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 Cerebrum cerebrum allows PHP Local File Inclusion.This issue affects Cerebrum: from n/a through <= 1.12.
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 Local File Inclusion (LFI) vulnerability exists in the Cerebrum PHP theme where user-controlled input is used in include/require statements without proper validation, allowing attackers to potentially read sensitive files from the server filesystem.
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
CerebrumWordPress extension
<= 1.12CVSS 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 Cerebrum theme versionCheck the theme's style.css header comment, version.php file, or theme configuration for the version number. Compare it to the affected range (<=1.12).Affected if Installed version is 1.12 or lower.
-
Locate include/require statements using user inputSearch PHP files in the theme for patterns like 'include($_GET', 'require($_REQUEST', or similar where superglobal arrays are used directly in inclusion statements without sanitization.Affected if Any include/require statement uses $_GET, $_POST, or $_REQUEST parameters without validation.
-
Identify vulnerable parametersReview the identified inclusion statements to find which specific parameter names (e.g., 'page', 'template', 'file', 'view') are used in the include/require calls.Affected if A parameter from user input is used in include/require without validation.
-
Check for path traversal validationExamine whether the code uses basename(), realpath(), or whitelist validation on the parameter before inclusion. Look for absent or weak validation patterns.Affected if No basename(), realpath(), or whitelist validation exists before the include/require.
-
Verify parameter is externally accessibleConfirm the vulnerable parameter can be passed via GET or POST requests to the application. Check if the code path handling this parameter is reachable without authentication.Affected if The vulnerable parameter can be controlled via HTTP requests without authentication barriers.
The environment is affected if Cerebrum version is 1.12 or lower AND user-controllable parameters are used in include/require statements without proper validation like basename().
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 whitelist-based input validation for any parameters used in include/require statements, use basename() to strip path traversal sequences, and consider using a mapping array instead of direct file name inclusion.
Fix this in Cerebrum
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-58926 — 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-58926 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