CVE-2024-6205 json
PayPlus Payment Gateway < 6.6.9 - Unauthenticated SQLi
published 2024-07-19 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-47342
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The PayPlus Payment Gateway WordPress plugin before 6.6.9 does not properly sanitise and escape a parameter before using it in a SQL statement via a WooCommerce API route available to unauthenticated users, leading to an SQL injection vulnerability.
Patch / fix
- Unknown PayPlus Payment Gateway 6.6.9
- payplus_ltd payplus_payment_gateway 6.6.9
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
4.13% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template PayPlus Payment Gateway < 6.6.9 - SQL Injection nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/7e2c5032-2917-418c-aee3-092bdb78a087/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Affected products
- Unknown PayPlus Payment Gateway
- payplus_ltd payplus_payment_gateway
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
wpscan.com
/vulnerability/7e2c5032-2917-418c-aee3-092bdb78a087/
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2024-6205
- NVD CVE-2024-6205
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.