PubzinneWordPress extension · Axiomthemes
CVE-2025-60060
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 Pubzinne pubzinne allows PHP Local File Inclusion.This issue affects Pubzinne: from n/a through <= 1.0.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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Pubzinne theme where improper control of filenames in include/require statements allows attackers to manipulate file paths and potentially execute arbitrary PHP code from local files.
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
PubzinneWordPress extension
<= 1.0.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 if Pubzinne theme is installedCheck your WordPress themes directory (wp-content/themes/pubzinne) or look for files containing 'pubzinne' or 'axiomthemes' in the theme folderAffected if The Pubzinne theme by axiomthemes is present in the WordPress installation
-
Determine installed Pubzinne versionCheck the style.css file in the theme root for the 'Version:' declaration, or check theme.json or any version file included with the themeAffected if The reported version is 1.0.12 or lower
-
Locate include/require statements in theme PHP filesSearch PHP files in the theme directory for patterns like 'include(', 'require(', 'include_once(', 'require_once(' that use variables in the file path argumentAffected if The theme contains include/require statements that accept variables in file paths without sanitization
-
Verify if user input reaches include/require pathsTrace the variables used in include/require statements to determine if they can be influenced by user-supplied input (GET, POST, COOKIE, or other request parameters)Affected if User-controlled data can be injected into file paths used in include/require statements
-
Check for common LFI entry pointsExamine common entry points like template files, callback handlers, or any file that processes URL parameters and passes them to include/requireAffected if URL parameters or other user input are directly or indirectly used in include/require file paths
You are affected if Pubzinne theme version 1.0.12 or lower is installed AND the theme contains include/require statements where file paths can be manipulated through user-supplied input.
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 dataUpgrade to a patched version if available; otherwise, implement strict input validation and allowlisting on all include/require statements, avoiding user-supplied input in file paths.
Fix this in Pubzinne
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60060 — 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-60060 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