CVE-2022-35697 json
AEM File Upload Security Issue leading to RXSS
published 4y ago modified 4mo ago also GHSA-qcgc-6q86-7x2p , EUVD-2022-6604
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
Adobe Experience Manager Core Components version 2.20.6 (and earlier) is affected by a reflected Cross-Site Scripting (XSS) vulnerability. If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser. Exploitation of this issue requires a low author privilege access.
Patch / fix
- maven com.adobe.cq:core.wcm.components.core 2.20.8
Is CVE-2022-35697 in your dependencies? 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
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.adobe.cq:core.wcm.components.core | <2.20.8 |
2.20.8 |
Affected products
- Adobe Experience Manager
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/adobe/aem-core-wcm-components/security/advisories/GHSA-qcgc-6q86-7x2p
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-35697
advisory
-
github.com
/adobe/aem-core-wcm-components
package
Sources
- CVE List CVE-2022-35697
- GitHub Advisory GHSA-qcgc-6q86-7x2p
- NVD CVE-2022-35697
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.