CVE-2022-4867 json
Cross-Site Request Forgery (CSRF) in froxlor/froxlor
published 2022-12-31 3 y ago modified 2026-06-17 4 mo ago also GHSA-6gwx-gw56-qhf7 , EUVD-2022-7531
- cvss
- 3.5
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.
Patch / fix
- packagist froxlor/froxlor 2.0.0-beta1
- froxlor froxlor/froxlor 2.0.0-beta1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/c91364dd-9ead-4bf3-96e6-663a017e08fa referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 3.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | froxlor/froxlor | >=2.0.0-beta0, <2.0.0-beta1 |
2.0.0-beta1 |
Affected products
- froxlor froxlor/froxlor
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/froxlor/froxlor/commit/f7f356e896173558248c43f4f68612f78e73a65d
web, patch, third-party-advisory
-
huntr.dev
/bounties/c91364dd-9ead-4bf3-96e6-663a017e08fa
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-4867
advisory
-
github.com
/froxlor/froxlor
package
Sources
- CVE List CVE-2022-4867
- GitHub Advisory GHSA-6gwx-gw56-qhf7
- NVD CVE-2022-4867
Fencer Vulns 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.