CVE-2020-35241 json
FlatPress 1.0.3 is affected by cross-site scripting (XSS) in the Blog Content component.
published 5y ago modified 4mo ago also EUVD-2020-22919
- cvss
- 4.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 1
- Exploit-DB
Summary
FlatPress 1.0.3 is affected by cross-site scripting (XSS) in the Blog Content component. This vulnerability can allow an attacker to inject the XSS payload in Blog content via the admin panel. Each time any user will go to that blog page, the XSS triggers and the attacker can steal the cookie according to the crafted payload.
Is CVE-2020-35241 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 FencerTimeline
- First public exploit (EDB-48826)
- Published
Exploit prediction
2.17% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-48826 Flatpress Add Blog 1.0.3 - Persistent Cross-Site Scripting webapps, 2020-09-22
- github.com https://github.com/hemantsolo/CVE-Reference/blob/main/CVE-2020-35241.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/hemantsolo/CVE-Reference/blob/main/CVE-2020-35241.md
exploit, third-party-advisory
-
flatpress.org
/download
product, vendor-advisory
- github.com /alpernae/vulnerability-research/tree/main/CVE-2020-35241
- exploit-db.com /exploits/48826
Sources
- CVE List CVE-2020-35241
- NVD CVE-2020-35241
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.