PrismaWordPress extension · Axiomthemes
CVE-2025-58932
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 Prisma prisma allows PHP Local File Inclusion.This issue affects Prisma: from n/a through <= 1.10.
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 axiomthemes Prisma WordPress theme where PHP include/require statements do not properly validate user-controlled input, allowing attackers to include arbitrary PHP files from the local filesystem. This can lead to code execution if an attacker can upload or access malicious PHP files on the server.
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
PrismaWordPress extension
<= 1.10CVSS 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 Prisma theme installationIn WordPress admin, go to Appearance > Themes and verify the Prisma theme is active. Note the installed version number displayed.Affected if Prisma theme version is 1.10 or lower
-
Compare version to affected rangeLocate the theme's style.css file in wp-content/themes/prisma/ and check the Version: header. Compare this version number against the affected range (1.10 and below).Affected if Version number is 1.10 or lower
-
Identify vulnerable include/require patternsSearch theme PHP files for include(), require(), include_once(), or require_once() statements where variables are used directly in the file path without sanitization (e.g., include($_GET['file']). Use grep or a code editor to scan .php files in the theme directory.Affected if Any include/require statements use unsanitized user input for file paths
-
Verify upload directory PHP execution statusCheck the wp-content/uploads directory configuration. Look for .htaccess files and server config (nginx/apache) to determine if PHP files can be executed from this directory.Affected if PHP execution is allowed in upload directories, making remote code execution possible if a file can be uploaded
You are affected if the Prisma theme version is 1.10 or lower AND your theme contains include/require statements that use unsanitized input for file paths, especially if PHP execution is permitted in upload directories.
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 Prisma theme to the latest version if a patch is available, otherwise implement strict allowlist-based validation for all file inclusion paths and disable PHP execution in upload directories.
Fix this in Prisma
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58932 — 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-58932 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