CVE-2025-14172
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 · uneditedThe WP Page Permalink Extension plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.5.4. This is due to missing authorization checks on the `cwpp_trigger_flush_rewrite_rules` function hooked to `wp_ajax_cwpp_trigger_flush_rewrite_rules`. This makes it possible for authenticated attackers, with Subscriber-level access and above, to flush the site's rewrite rules via the `action` parameter.
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 confidenceThe WP Page Permalink Extension plugin for WordPress has a missing authorization vulnerability in all versions up to 1.5.4. The AJAX action `cwpp_trigger_flush_rewrite_rules` lacks capability checks, allowing any authenticated user with Subscriber-level access or higher to trigger WordPress rewrite rule flushing via the `action` parameter.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 WP Page Permalink Extension is installedCheck the WordPress plugins directory for the plugin folder (typically named 'wp-page-permalink-extension' or similar) or query the wp_options table for active plugin entriesAffected if Plugin files exist in the plugins directory or is listed in WordPress active plugins
-
Check installed versionOpen the main plugin PHP file and locate the Version header in the plugin comment block, then compare against 1.5.4Affected if Version is 1.5.4 or lower
-
Verify AJAX endpoint existsCheck the plugin source code for the add_action call registering 'cwpp_trigger_flush_rewrite_rules' to wp_ajax_, or test the endpoint by sending a POST request to /wp-admin/admin-ajax.php with action=cwpp_trigger_flush_rewrite_rulesAffected if The AJAX action cwpp_trigger_flush_rewrite_rules is registered and responds to requests
-
Check authorization on the endpointSubmit a request to the AJAX endpoint while authenticated as a user with the Subscriber role (the lowest privileged role) and verify the request is processed rather than rejectedAffected if A user with Subscriber-level access can successfully trigger the endpoint without receiving a capability error
If the plugin is installed at version 1.5.4 or earlier and the AJAX endpoint accepts requests from users with Subscriber-level access without proper capability verification, the environment is affected by CVE-2025-14172
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 plugin to version 1.5.5 or later which includes proper authorization checks on the affected AJAX endpoint to verify user capabilities before allowing rewrite rule operations.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14172 — 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-14172 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