Security readout for executives and security teams
Plain-English summary
Publify versions v8.0 through v9.2.4 can let a publisher-level user upload an HTML file containing stored JavaScript. If another user opens that uploaded content, the script may run in their browser, creating confidentiality and integrity risk within the site.
Executive priority
Treat this as a moderate priority. It is not listed as known exploited, but it affects authenticated publishing workflows and can expose administrators or editors to browser-based compromise when malicious uploaded content is viewed.
Technical view
This is a stored XSS issue classified as CWE-79. The CVSS 3.1 score is 5.4, with network access, low attack complexity, low privileges, required user interaction, changed scope, and low confidentiality and integrity impact.
Likely exposure
Exposure is most likely in Publify or publify_core deployments running v8.0 through v9.2.4 where publisher-role users can upload files. Public-facing blogs or CMS instances with multiple content contributors have the clearest risk.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires publisher-level access and a victim opening or rendering the uploaded malicious HTML content. No exploit steps are provided here.
Researcher notes
Evidence supports stored XSS via unrestricted HTML upload by publisher-role users. The supplied source bundle names the affected range but does not provide a clear fixed release. One reference appears mislabeled as CVE-2021-25974, so verify vendor context carefully.
Mitigation direction
- Inventory Publify deployments and identify versions v8.0 through v9.2.4.
- Check Publify vendor guidance and commit d99c0870 before selecting the upgrade path.
- Restrict publisher-role access to trusted users until remediation is complete.
- Review uploaded HTML files and remove suspicious or unnecessary content.
- Limit or disable HTML uploads where operationally feasible.
Validation and detection
- Confirm the running Publify or publify_core version on each deployment.
- Review user accounts assigned the publisher role.
- Check content storage for uploaded HTML files from publisher users.
- Verify remediation against vendor guidance in a staging environment.
- Confirm file upload restrictions match the intended security policy.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-25975 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25974CVE reference · x_refsource_MISC
- https://github.com/publify/publify/commit/d99c0870d3dbbfde7febdc6cad33199b84770101CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.