Paid Memberships Pro < 2.3.3 - Authenticated SQL Injection
Strategic Overview
- Status
- Patched in 2.3.3
- Affected Version
< 2.3.3- CVSS
- 4.7Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2020-5579
At a glance
CVE-2020-5579 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Paid Memberships Pro WordPress plugin, affecting versions < 2.3.3. It carries a CVSS score of 4.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 2.3.3; sites on affected versions should update now. Disclosed May 2020, reported by Kenichi Okuno (Mitsui Bussan Secure Directions).
Vulnerability Overview
SQL injection vulnerability in the Paid Memberships versions prior to 2.3.3 allows attacker with administrator rights to execute arbitrary SQL commands via unspecified vectors. The 'discount_code_id' found in the ~/adminpages/orders.php is the specific parameter that is vulnerable.
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 interaction from a victim user.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Paid Memberships Pro < 2.3.3 carries this weakness at discount_code_id, and reaching it takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Paid Memberships Pro the fix is 2.3.3: builds < 2.3.3 are affected, anything from 2.3.3 onward is not.
Remediation
Update to version 2.3.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Paid Memberships Pro: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Paid Memberships Pro 2.3.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 9.8CVE-2023-23488: Paid Memberships Pro < 2.9.8 SQL Injection
CVE-2023-23488 - 9.8CVE-2021-25114: Paid Memberships Pro <= 2.6.6 SQL Injection
CVE-2021-25114 - 9.1CVE-2024-37486: Paid Memberships Pro <= 3.0.5 SQL Injection
CVE-2024-37486 - 8.8CVE-2021-20678: Paid Memberships Pro <= 2.5.5 SQL Injection
CVE-2021-20678
Other vulnerabilities in Paid Memberships Pro – Content Restriction, User Registration, & Paid Subscriptions
- 7.7CVE-2023-0631: Paid Memberships Pro <= 2.9.11 SQL Injection
CVE-2023-0631 - 7.5CVE-2023-6187: Paid Memberships Pro <= 2.12.3 Arbitrary File Upload
CVE-2023-6187 - 7.5CVE-2014-8801: Paid Memberships Pro < 1.7.15 Directory Traversal
CVE-2014-8801 - 7.2Paid Memberships Pro <= 2.0.5 Open Redirect
- 7.1CVE-2026-4100: Paid Memberships Pro Authenticated (Subscriber+)
CVE-2026-4100 - 6.4CVE-2026-15016: Paid Memberships Pro Stored XSS
CVE-2026-15016 - 6.4CVE-2022-4830: Paid Memberships Pro <= 2.9.8 Stored XSS
CVE-2022-4830 - 6.4Paid Memberships Pro XSS
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C