Pretty Url
pretty-url · plugin
Known security vulnerabilities for Pretty Url. Find out in seconds which version runs on your site with WP Lens.
3 known vulnerabilities
2 exploitable without logging in · 1 with no official fix seen · 1 with public exploit code · latest Jan 31, 2025
Before you install
Do not install
- 1 record shows no fix in the latest wordpress.org release.
- 2 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.5.5 · last updated Jun 18, 2025 · 70+ installs
wordpress.org status checked on Nov 19, 2026
Vulnerabilities
- High 7.1
CVE-2025-22564unauthenticated · needs a click≤ 1.5.4
WordPress Pretty Url Plugin <= 1.5.4 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 4.8
CVE-2023-2009admin≤ 1.5.4
Pretty Url <= 1.5.4 - Admin+ Stored XSS in plugin settings
- Medium 4.3
CVE-2025-22563unauthenticated · needs a clickno fix seen
WordPress Pretty Urls Plugin <= 1.5.5 - Cross Site Request Forgery (CSRF) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (1.5.5) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.