CVE-2022-4096 json
Server-Side Request Forgery (SSRF) in appsmithorg/appsmith
published 3y ago modified last mo. also BIT-appsmith-2022-4096 , EUVD-2022-51466
- cvss
- 8.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Server-Side Request Forgery (SSRF) in GitHub repository appsmithorg/appsmith prior to 1.8.2.
Patch / fix
- bitnami appsmith 1.8.2
- appsmithorg appsmithorg/appsmith 1.8.2
Is CVE-2022-4096 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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/7969e834-5982-456e-9683-861a7a5e2d22 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | appsmith | <1.8.2 |
1.8.2 |
Affected products
- appsmithorg appsmithorg/appsmith
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/appsmithorg/appsmith/commit/769719ccfe667f059fe0b107a19ec9feb90f2e40
patch, third-party-advisory, advisory
-
huntr.dev
/bounties/7969e834-5982-456e-9683-861a7a5e2d22
exploit, issue-tracking, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-4096
web
Sources
- CVE List CVE-2022-4096
- NVD CVE-2022-4096
- OSV BIT-appsmith-2022-4096
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.