CVE-2025-60193
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 User Roles premmerce-user-roles allows PHP Local File Inclusion.This issue affects Premmerce User Roles: from n/a through <= 1.0.13.
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 confidencePremmerce User Roles WordPress plugin versions <= 1.0.13 contains a PHP Local File Inclusion (LFI) vulnerability where user-controlled input is used in include/require statements without proper sanitization, allowing attackers to include arbitrary local PHP 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 Premmerce User Roles plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Premmerce User Roles' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'premmerce-user-roles' or similar.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin Plugins list, click 'View Details' on the Premmerce User Roles plugin to see the version number. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comment block.Affected if The installed version is 1.0.13 or lower
-
Locate file inclusion handlersSearch the plugin directory for PHP files containing 'include', 'require', 'include_once', or 'require_once' statements. Look for dynamic file paths using variables like $_GET, $_POST, or $_REQUEST.Affected if The plugin contains include/require statements that accept user-controlled input
-
Identify vulnerable parametersExamine identified file inclusion code for parameters that could accept file paths (commonly 'file', 'path', 'template', 'page', 'action'). Check if these parameters are sanitized before use in include/require.Affected if User-supplied parameters flow directly into include/require without sanitization or validation
-
Test for directory traversalIf a parameter is identified, attempt a controlled test request with traversal sequences (e.g., ../../wp-config.php) to see if the application allows arbitrary file inclusion. Only do this in non-production environments.Affected if The application permits directory traversal patterns in file inclusion parameters
A user is affected if Premmerce User Roles plugin version 1.0.13 or lower is installed AND the plugin contains file inclusion logic that uses unsanitized user input from request parameters.
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 Premmerce User Roles to the latest patched version. If no patch is available, disable the plugin and implement input validation/sanitization on file inclusion paths, or deploy a WAF rule to block directory traversal sequences.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60193 — 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-60193 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