CVE-2025-50003
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 Amuli amuli allows PHP Local File Inclusion.This issue affects Amuli: from n/a through <= 2.3.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 · high confidenceLocal File Inclusion vulnerability in the Amuli WordPress theme from axiomthemes allows attackers to control filenames used in PHP include/require statements. This can be exploited to read sensitive files from the server or achieve remote code execution if attackers can upload or control included files. The CVSS 8.1 score reflects the high potential impact of unauthorized file access or RCE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 Amuli theme installationNavigate to WordPress admin > Appearance > Themes and check if the Amuli theme by axiomthemes is installed and activatedAffected if The Amuli theme is present and active in WordPress
-
Identify installed theme versionAccess the theme directory via FTP or file manager, locate the style.css file in /wp-content/themes/amuli/, and read the 'Version:' header from the file commentsAffected if A version of Amuli theme is installed (any version without the patch is potentially vulnerable)
-
Search for unsafe file inclusion patternsIn the theme directory, search all PHP files for patterns like 'include(', 'require(', 'include_once(', 'require_once(' combined with '$_GET', '$_REQUEST', or '$theme_root' to identify potential LFI entry pointsAffected if Theme files contain dynamic include/require statements using unfiltered user input parameters
-
Inspect include/require parameter handlingFor any found include/require calls using $_GET or $_REQUEST, examine whether the parameter values are sanitized (e.g., using basename(), whitelist checks) before being used in file operationsAffected if Parameters used in file inclusion are not validated or sanitized, allowing path traversal (e.g., ../../etc/passwd)
-
Review web server access logsSearch Apache/Nginx access logs for requests to theme PHP files containing patterns like '?file=', '?template=', '?page=' with directory traversal sequences ('../') or sensitive pathsAffected if Logs show exploitation attempts or suspicious file inclusion parameter usage targeting the theme
You are affected if the Amuli theme from axiomthemes is installed and its PHP code contains file inclusion logic that uses unvalidated user-supplied parameters, allowing attackers to control which files are included.
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 the Amuli theme to the latest patched version immediately. If no patch is available, deactivate the theme and implement web application firewall rules to block suspicious include/require parameter patterns until a fix is released.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50003 — 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-50003 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