CVE-2022-3849 json
WP User Merger < 1.5.3 - Admin+ SQLi via user_id
published 3y ago modified 4mo ago also EUVD-2022-43189
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
The WP User Merger WordPress plugin before 1.5.3 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 admin
Patch / fix
- Unknown WP User Merger 1.5.3
Is CVE-2022-3849 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/511327d3-499b-4ad9-8fd3-99f9f7deb4f5 referenced PoC, tagged "exploit" by a source, unverified
- bulletin.iese.de https://bulletin.iese.de/post/wp-user-merger_1-5-1_3/ 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 WP User Merger
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/511327d3-499b-4ad9-8fd3-99f9f7deb4f5
exploit, vdb-entry, technical-description, third-party-advisory
-
bulletin.iese.de
/post/wp-user-merger_1-5-1_3/
exploit, third-party-advisory
Sources
- CVE List CVE-2022-3849
- NVD CVE-2022-3849
Fencer Intel 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.