Pretty Links – Affiliate Links, Link Branding, Link Tracking & Marketing Plugin <= 3.6.3 - Cross-Site Request Forgery to Plugin Settings Update
Strategic Overview
- Status
- Patched in 3.6.4
- Affected Plugin
- PrettyLinks – Affiliate Link Management, URL Shortener, Link Cloaking, Tracking & Branded Short Links
- Affected Version
<= 3.6.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-2326
At a glance
CVE-2024-2326 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the PrettyLinks WordPress plugin, affecting versions <= 3.6.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.6.4; sites on affected versions should update now. Disclosed March 2024, reported by Webbernaut.
Vulnerability Overview
The Pretty Links – Affiliate Links, Link Branding, Link Tracking & Marketing Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6.3. This is due to missing or incorrect nonce validation when saving plugin settings. This makes it possible for unauthenticated attackers to change the plugin's configuration including stripe integration via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in PrettyLinks <= 3.6.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For PrettyLinks the fix is 3.6.4: builds <= 3.6.3 are affected, anything from 3.6.4 onward is not.
Remediation
Update to version 3.6.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to PrettyLinks: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PrettyLinks 3.6.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in PrettyLinks – Affiliate Link Management, URL Shortener, Link Cloaking, Tracking & Branded Short Links
- 7.2CVE-2019-25147: Pretty Links <= 2.1.9 Stored Cross-Site Scripting
CVE-2019-25147 - 7.2CVE-2015-9457: Pretty Links SQL Injection
CVE-2015-9457 - 7.2CVE-2013-1636: Pretty Links Lite < 1.6.3 Stored Cross-Site Scripting
CVE-2013-1636 - 6.1CVE-2024-29770: Shortlinks by Pretty Links <= 3.6.2 Reflected XSS
CVE-2024-29770 - 6.1CVE-2011-4595: Pretty Links Reflected XSS
CVE-2011-4595 - 4.9CVE-2026-5062: PrettyLinks <= 3.6.20 SQL Injection
CVE-2026-5062 - 4.3CVE-2025-48247: Shortlinks by Pretty Links Missing Authorization
CVE-2025-48247
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C