CVE-2021-25975 json
Publify - Stored Cross-Site Scripting (XSS) due to Unrestricted File Upload
published 2021-11-10 4 y ago modified 2026-06-17 4 mo ago also BIT-publify-2021-25975 , EUVD-2022-2187 , GHSA-3h7v-wqw7-ff28
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
In publify, versions v8.0 to v9.2.4 are vulnerable to stored XSS as a result of an unrestricted file upload. This issue allows a user with “publisher” role to inject malicious JavaScript via the uploaded html file.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/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 |
| OSV | 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 |
|---|---|---|---|
| rubygems | publify_core | >=8.0, <9.2.5 |
9.2.5 |
| bitnami | publify | >=8.0.0, <9.2.4 |
9.2.4 |
Affected products
- publify_core publify_core
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/publify/publify/commit/d99c0870d3dbbfde7febdc6cad33199b84770101
web, patch, third-party-advisory
-
whitesourcesoftware.com
/vulnerability-database/CVE-2021-25974
web, not-applicable, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-25975
advisory
-
github.com
/publify/publify
package
Sources
- CVE List CVE-2021-25975
- GitHub Advisory GHSA-3h7v-wqw7-ff28
- NVD CVE-2021-25975
- OSV BIT-publify-2021-25975
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.