UnicampWordPress extension · Thememove
CVE-2025-54701
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 ThemeMove Unicamp unicamp allows PHP Local File Inclusion.This issue affects Unicamp: from n/a through <= 2.6.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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the ThemeMove Unicamp theme (versions up to 2.6.3). The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file paths and potentially execute arbitrary PHP code or access sensitive 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
UnicampWordPress extension
< 2.6.4CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Verify Unicamp theme installationLocate the Unicamp theme directory in the WordPress installation, typically under wp-content/themes/unicamp. Confirm the theme files are present on the server.Affected if The Unicamp theme files exist in the WordPress themes directory.
-
Determine installed versionCheck the style.css file in the theme directory for the 'Version:' header, or look for a version constant in theme configuration files.Affected if The installed version is below 2.6.4 (versions 2.6.3 and earlier are affected).
-
Confirm theme is activeIn WordPress admin dashboard, go to Appearance > Themes and verify if Unicamp is the currently active theme.Affected if The Unicamp theme is activated on the WordPress site.
-
Identify vulnerable file inclusion patternsSearch the theme source code for include, require, include_once, or require_once statements that accept user-controlled parameters (commonly through $_GET, $_POST, or request variables). Examine any file parameter handlers.Affected if The theme contains include/require statements that process external input as file paths without proper sanitization.
-
Check for accessible file path parametersReview the theme PHP files for parameters (such as 'file', 'path', 'page', 'template', or similar) that could be passed via URL to control file inclusion. Test if these parameters can be manipulated to traverse directories.Affected if URL-accessible parameters exist that can be manipulated to include arbitrary files from the server filesystem.
A user is affected if the Unicamp theme version is below 2.6.4, the theme is active, and the vulnerable file inclusion code with user-controllable parameters is accessible on the 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 data2.6.4
Update Unicamp theme to the latest patched version. If no update is available, implement input validation and sanitization for all file path parameters, disable PHP execution in upload directories, and consider web application firewall rules to block directory traversal attempts.
Fix this in Unicamp
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54701 — 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-54701 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