IpharmWordPress extension · Axiomthemes
CVE-2025-60047
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 IPharm ipharm allows PHP Local File Inclusion.This issue affects IPharm: from n/a through <= 1.2.3.
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 · high confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the IPharm WordPress theme/Plugin from axiomthemes. The vulnerability allows attackers to manipulate filename parameters in include/require statements to read arbitrary files on the server via path traversal (e.g., ../../wp-config.php).
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
IpharmWordPress extension
<= 1.2.3CVSS 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 Ipharm theme/plugin is installedCheck your WordPress installation for the axiomthemes Ipharm theme or plugin. Look in wp-content/themes/ for 'ipharma' or 'ipharma-child' folders, or check Plugins page for axiomthemes Ipharm.Affected if The Ipharm theme or plugin from axiomthemes is present in the WordPress installation
-
Determine installed Ipharm versionOpen the style.css file in the Ipharm theme folder and look for the 'Version:' header in the file comments, or check the plugin header if installed as a plugin.Affected if The version listed is 1.2.3 or lower
-
Locate vulnerable file inclusion codeSearch the Ipharm theme/plugin files for PHP include, require, include_once, or require_once statements that use variables in the file path. Look for patterns like 'include($filename)' or 'require($_GET[...]' in PHP files.Affected if File inclusion code using dynamic variables without validation is found
-
Check if vulnerable parameter is accessibleIf the file inclusion code uses GET or POST parameters (common names: file, page, template, filename, path), test if these parameters can be manipulated via HTTP requests to trigger path traversal.Affected if The file inclusion parameter accepts user input and can be accessed via HTTP without authentication
You are affected if Ipharm version 1.2.3 or lower is installed AND the vulnerable dynamic file inclusion code with user-controlled parameters is accessible on your server.
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 sanitization for all file inclusion parameters, using whitelist-based approaches or built-in PHP functions like realpath() to prevent path traversal attacks. Alternatively, remove the vulnerable include/require functionality entirely if not essential.
Fix this in Ipharm
Scoped from the published advisory
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60047 — 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-60047 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