CVE-2022-23497 json
Insecure file access in FreshRSS
published 2022-12-09 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-28550
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
FreshRSS is a free, self-hostable RSS aggregator. User configuration files can be accessed by a remote user. In addition to user preferences, such configurations contain hashed passwords (brypt with cost 9, salted) of FreshRSS Web interface. If the API is used, the configuration might contain a hashed password (brypt with cost 9, salted) of the GReader API, and a hashed password (MD5 salted) of the Fever API. Users should update to version 1.20.2 or edge. Users unable to upgrade can apply the patch manually or delete the file `./FreshRSS/p/ext.php`.
Patch / fix
- freshrss freshrss 1.20.2
- github.com/FreshRSS/FreshRSS#4928 pull request
- github.com/FreshRSS/FreshRSS/releases/tag/1.20.2 release
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.91% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- FreshRSS FreshRSS
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/FreshRSS/FreshRSS/pull/4928
patch, third-party-advisory
-
github.com
/FreshRSS/FreshRSS/releases/tag/1.20.2
patch, third-party-advisory
-
github.com
/FreshRSS/FreshRSS/security/advisories/GHSA-hvrj-5fwj-p7v6
third-party-advisory
Sources
- CVE List CVE-2022-23497
- NVD CVE-2022-23497
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.