CVE-2022-3847 json
Showing URL in QR Code <= 0.0.1 - Stored XSS via CSRF
published 3y ago modified 4mo ago also EUVD-2022-43187
- cvss
- 6.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
The Showing URL in QR Code WordPress plugin through 0.0.1 does not have CSRF check when updating its settings, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin or editor add Stored XSS payloads via a CSRF attack
Is CVE-2022-3847 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 FencerExploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/a70ad549-2e09-44fb-b894-4271ad4a84f6 referenced PoC, tagged "exploit" by a source, unverified
- bulletin.iese.de https://bulletin.iese.de/post/get-site-to-phone-by-qr-code_0-0-1/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Unknown Showing URL in QR Code
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/a70ad549-2e09-44fb-b894-4271ad4a84f6
exploit, vdb-entry, technical-description, third-party-advisory
-
bulletin.iese.de
/post/get-site-to-phone-by-qr-code_0-0-1/
exploit, third-party-advisory
Sources
- CVE List CVE-2022-3847
- NVD CVE-2022-3847
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.