CVE-2025-60200
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 ThimPress LearnPress Export Import learnpress-import-export allows PHP Local File Inclusion.This issue affects LearnPress Export Import: from n/a through <= 4.1.2.
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 LearnPress Export Import WordPress plugin. The flaw allows attackers to manipulate file inclusion paths due to improper input validation, potentially executing arbitrary PHP code by including malicious local files.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 LearnPress Export Import plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'LearnPress Export Import' or check the /wp-content/plugins/ directory for the learnpress-export-import folderAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionCheck the plugin main file (usually learnpress-export-import.php) for the 'Version' header in the plugin comments, or view the plugin details in WordPress admin plugins listAffected if The version is unknown, unpatched, or within any known vulnerable version range
-
Verify the export/import functionality is accessibleCheck if the plugin endpoints are accessible by examining the plugin's ajax handlers or public-facing import/export functions in the code - look for includes or require statements that use user inputAffected if The plugin's import/export code processes file paths without proper sanitization and is accessible to users
-
Inspect for unauthorized file modificationsCompare plugin files against known good copies from the WordPress repository using file integrity monitoring or manual checksum comparisonAffected if Files have been modified or suspicious PHP files exist in the plugin directory that were not part of the original distribution
-
Review access logs for path traversal attemptsExamine web server access logs (Apache/nginx) for requests to the plugin containing patterns like '../', '..\', or absolute paths in parameters related to import/export functionalityAffected if Logs show directory traversal attempts targeting the plugin's file inclusion functions
A user is affected if the LearnPress Export Import plugin is installed and its vulnerable file inclusion functionality is accessible without proper input validation being applied.
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 LearnPress Export Import to the latest patched version immediately. If no patched version is available, disable the plugin and consider deploying a WAF rule to block directory traversal attempts as a temporary measure.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60200 — 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-60200 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