CVE-2022-4596 json
Shoplazza Add Blog Post cross site scripting
published 3y ago modified 4mo ago also EUVD-2022-51928
- cvss
- 3.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as problematic, has been found in Shoplazza 1.1. This issue affects some unknown processing of the file /admin/api/admin/articles/ of the component Add Blog Post Handler. The manipulation of the argument Title leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-216191.
Is CVE-2022-4596 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.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- seclists.org https://seclists.org/fulldisclosure/2022/Dec/att-11/proof-of-concept-shoplazza.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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 |
Affected products
- unspecified Shoplazza
Classification
- Weakness
-
- CWE-707 Improper Neutralization
References
-
seclists.org
/fulldisclosure/2022/Dec/att-11/proof-of-concept-shoplazza.txt
exploit, mailing-list, third-party-advisory
-
seclists.org
/fulldisclosure/2022/Dec/11
mailing-list, third-party-advisory
-
vuldb.com
/?id.216191
permissions-required, third-party-advisory
Sources
- CVE List CVE-2022-4596
- NVD CVE-2022-4596
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.