PrettyLinks at a glance
- 9 publicly disclosed vulnerabilities, 3 of them rated High or Critical. The most recent was disclosed on Aug 4, 2026.
- Ranked #230 by popularity on WordPress.org (200,000+ active installs).
- The latest version is 4.0.18 (released Oct 21, 2026). The most recent security fix shipped in 3.6.21.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your PrettyLinks version
Enter the PrettyLinks version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “PrettyLinks”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “PrettyLinks”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (4.0.18). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known PrettyLinks vulnerabilities
PrettyLinks <= 3.6.20 - Authenticated (Administrator+) SQL Injection via 's' Parameter
SQL injection · CVE-2026-5062
Affected versions: ≤ 3.6.20
Fixed in: 3.6.21
Severity: Medium 4.9 · Disclosed Aug 4, 2026
Shortlinks by Pretty Links <= 3.6.15 - Missing Authorization
Missing authorization · CVE-2025-48247
Affected versions: ≤ 3.6.15
Fixed in: 3.6.16
Severity: Medium 4.3 · Disclosed May 19, 2025
Shortlinks by Pretty Links <= 3.6.2 - Reflected Cross-Site Scripting via post_status
Cross-site scripting (XSS) · CVE-2024-29770
Affected versions: ≤ 3.6.2
Fixed in: 3.6.3
Severity: Medium 6.1 · Disclosed Mar 25, 2024
Pretty Links – Affiliate Links, Link Branding, Link Tracking & Marketing Plugin <= 3.6.3 - Cross-Site Request Forgery to Plugin Settings Update
Cross-site request forgery (CSRF) · CVE-2024-2326
Affected versions: ≤ 3.6.3
Fixed in: 3.6.4
Severity: Medium 4.3 · Disclosed Mar 22, 2024
Shortlinks by Pretty Links <= 3.4.0 - Cross-Site Request Forgery via route
Cross-site request forgery (CSRF) · CVE-2022-47149
Affected versions: ≤ 3.4.0
Fixed in: 3.4.1
Severity: Medium 4.3 · Disclosed Apr 13, 2023
Pretty Links <= 2.1.9 - Unauthenticated Stored Cross-Site Scripting via track_link
Cross-site scripting (XSS) · CVE-2019-25147
Affected versions: < 2.1.10
Fixed in: 2.1.10
Severity: High 7.2 · Disclosed Jun 19, 2019
Pretty Links – Link Management, Branding, Tracking & Sharing Plugin <= 1.6.7 - SQL Injection
SQL injection · CVE-2015-9457
Affected versions: < 1.6.8
Fixed in: 1.6.8
Severity: High 7.2 · Disclosed Jul 8, 2015
Pretty Links Lite < 1.6.3 - Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2013-1636
Affected versions: < 1.6.3
Fixed in: 1.6.3
Severity: High 7.2 · Disclosed Aug 1, 2014
Pretty Links – Link Management, Branding, Tracking & Sharing Plugin < 1.5.6 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2011-4595
Affected versions: < 1.5.6
Fixed in: 1.5.6
Severity: Medium 6.1 · Disclosed Dec 4, 2011
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| PrettyLinks <= 3.6.20 - Authenticated (Administrator+) SQL Injection via 's' ParameterSQL injection · CVE-2026-5062 | ≤ 3.6.20 | 3.6.21 | Medium 4.9 | Aug 4, 2026 |
| Shortlinks by Pretty Links <= 3.6.15 - Missing AuthorizationMissing authorization · CVE-2025-48247 | ≤ 3.6.15 | 3.6.16 | Medium 4.3 | May 19, 2025 |
| Shortlinks by Pretty Links <= 3.6.2 - Reflected Cross-Site Scripting via post_statusCross-site scripting (XSS) · CVE-2024-29770 | ≤ 3.6.2 | 3.6.3 | Medium 6.1 | Mar 25, 2024 |
| Pretty Links – Affiliate Links, Link Branding, Link Tracking & Marketing Plugin <= 3.6.3 - Cross-Site Request Forgery to Plugin Settings UpdateCross-site request forgery (CSRF) · CVE-2024-2326 | ≤ 3.6.3 | 3.6.4 | Medium 4.3 | Mar 22, 2024 |
| Shortlinks by Pretty Links <= 3.4.0 - Cross-Site Request Forgery via routeCross-site request forgery (CSRF) · CVE-2022-47149 | ≤ 3.4.0 | 3.4.1 | Medium 4.3 | Apr 13, 2023 |
| Pretty Links <= 2.1.9 - Unauthenticated Stored Cross-Site Scripting via track_linkCross-site scripting (XSS) · CVE-2019-25147 | < 2.1.10 | 2.1.10 | High 7.2 | Jun 19, 2019 |
| Pretty Links – Link Management, Branding, Tracking & Sharing Plugin <= 1.6.7 - SQL InjectionSQL injection · CVE-2015-9457 | < 1.6.8 | 1.6.8 | High 7.2 | Jul 8, 2015 |
| Pretty Links Lite < 1.6.3 - Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2013-1636 | < 1.6.3 | 1.6.3 | High 7.2 | Aug 1, 2014 |
| Pretty Links – Link Management, Branding, Tracking & Sharing Plugin < 1.5.6 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2011-4595 | < 1.5.6 | 1.5.6 | Medium 6.1 | Dec 4, 2011 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Aug 4, 2026.
Most common weaknesses in PrettyLinks
Cross-site scripting (XSS)
4 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
SQL injection
2 issues
Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.
Cross-site request forgery (CSRF)
2 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
Frequently asked questions
Is PrettyLinks safe to use?
PrettyLinks is a well-known plugin with 200,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (4.0.18) and turn on automatic updates.
How do I find which version of PrettyLinks my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.