CVE-2022-4306 json
Panda Pods Repeater Field < 1.5.4 - Reflected XSS
published 3y ago modified 4mo ago also EUVD-2022-51661
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The Panda Pods Repeater Field WordPress plugin before 1.5.4 does not sanitize and escapes a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against a user having at least Contributor permission.
Patch / fix
- Unknown Panda Pods Repeater Field 1.5.4
Is CVE-2022-4306 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
0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template WordPress Panda Pods Repeater Field <1.5.4 - Cross-Site Scripting nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/18d7f9af-7267-4723-9d6f-05b895c94dbe referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Unknown Panda Pods Repeater Field
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/18d7f9af-7267-4723-9d6f-05b895c94dbe
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2022-4306
- NVD CVE-2022-4306
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.