CVE-2022-3768 json
WPSmartContracts < 1.3.12 - Author+ SQLi
published 2022-11-28 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-43120
- cvss
- 8.8
- 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 WPSmartContracts WordPress plugin before 1.3.12 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by users with a role as low as author
Patch / fix
- Unknown WPSmartContracts 1.3.12
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 18 mo ago
Exploit prediction
4.07% 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 WordPress WPSmartContracts <1.3.12 - SQL Injection nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/1d8bf5bb-5a17-49b7-a5ba-5f2866e1f8a3 referenced PoC, tagged "exploit" by a source, unverified
- bulletin.iese.de https://bulletin.iese.de/post/wp-smart-contracts_1-3-11/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown WPSmartContracts
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
wpscan.com
/vulnerability/1d8bf5bb-5a17-49b7-a5ba-5f2866e1f8a3
exploit, vdb-entry, technical-description, third-party-advisory
-
bulletin.iese.de
/post/wp-smart-contracts_1-3-11/
exploit, third-party-advisory
Sources
- CVE List CVE-2022-3768
- NVD CVE-2022-3768
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.