CVE-2022-2546 json
All-in-One WP Migration < 7.63 - Unauthenticated Reflected XSS
published 3y ago modified 4mo ago also EUVD-2022-34800
- cvss
- 4.7
- 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 68%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The All-in-One WP Migration WordPress plugin before 7.63 uses the wrong content type, and does not properly escape the response from the ai1wm_export AJAX action, allowing an attacker to craft a request that when submitted by any visitor will inject arbitrary html or javascript into the response that will be executed in the victims session. Note: This requires knowledge of a static secret key
Patch / fix
- Unknown All-in-One WP Migration 7.63
Is CVE-2022-2546 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
- partial
- Assessed
- last yr.
Exploit prediction
1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template WordPress All-in-One WP Migration <=7.62 - Cross-Site Scripting nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/f84920e4-a1fe-47cf-9ba5-731989c70f58 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 4.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 4.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Unknown All-in-One WP Migration
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/f84920e4-a1fe-47cf-9ba5-731989c70f58
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2022-2546
- NVD CVE-2022-2546
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.