CVE-2025-60241
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 Premmerce Premmerce premmerce allows PHP Local File Inclusion.This issue affects Premmerce: from n/a through <= 1.3.19.
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 confidencePremmerce WordPress plugin versions up to 1.3.19 contain a PHP Local File Inclusion vulnerability where user-controlled input is improperly used in include/require statements without adequate validation, allowing attackers to read sensitive local files on the server.
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 Premmerce plugin is installedLog in to WordPress admin, navigate to Plugins > Installed Plugins, and look for 'Premmerce' in the list. Alternatively, check the /wp-content/plugins/ directory for a premmerce folder.Affected if The Premmerce plugin is present in the WordPress installation
-
Check installed Premmerce versionIn WordPress admin under Plugins, find Premmerce and view the version number displayed beneath the plugin name. If using WP-CLI, run: wp plugin list --filter=name=premmerce --format=jsonAffected if The installed version is 1.3.19 or any version lower than 1.3.19
-
Identify accessible entry points with user inputReview the Premmerce plugin files for PHP include/require statements that use $_GET, $_POST, or similar superglobals without proper sanitization. Common patterns to search: include($_REQUEST[...]), require($_GET[...]), include_once($_POST[...]).Affected if The plugin contains include/require code that uses unsanitized user input from URL parameters or form submissions
-
Verify the vulnerable code path is reachableTest whether the parameter used in the insecure include/require is accessible via HTTP request to the WordPress site. Attempt to access a known sensitive file (e.g., /wp-config.php) through the identified parameter.Affected if The vulnerable parameter is exposed and allows path traversal (e.g., ../../wp-config.php) without being blocked
The environment is affected if Premmerce plugin version 1.3.19 or lower is installed and contains code that uses user-supplied input in include/require statements without validation.
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 of Premmerce. If no patch available, implement strict input validation on all include/require paths and disable allow_url_include.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60241 — 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-60241 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