Security readout for executives and security teams
Plain-English summary
Publify let a publisher-level user save JavaScript inside pages or articles. When another user views that content, the script may run in their browser. This can support account/session abuse or content tampering, but it requires an authenticated publisher and victim interaction, so urgency is moderate.
Executive priority
Prioritize remediation in the next regular security patch cycle, sooner if Publify has many publisher accounts or administrator users regularly review submitted content. This is not evidenced as actively exploited, but stored XSS can turn a compromised low-privilege account into broader browser-side impact.
Technical view
CVE-2021-25974 is stored XSS, CWE-79, in Publify v8.0 through v9.2.4. The editor allowed a publisher role to inject arbitrary JavaScript while creating a page or article. CVSS 3.1 is 5.4 with low privileges required, user interaction required, changed scope, and low confidentiality/integrity impact.
Likely exposure
Exposure is likely limited to Publify deployments running v8.0-v9.2.4 where publisher accounts can create pages or articles. Risk increases with shared editorial access, contractors, compromised publisher accounts, or public-facing content viewed by administrators.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, or confirmed public exploitation. Exploitation requires authenticated publisher access and a user viewing the stored content. Treat this as a credible internal or compromised-account risk, not confirmed internet-scale exploitation.
Researcher notes
Evidence supports stored XSS in the editor path for page/article creation by publisher users. The bundle names affected versions through v9.2.4 and references a fix commit. It does not provide enough evidence to claim active exploitation, unauthenticated reachability, or specific post-exploitation outcomes beyond browser-executed JavaScript.
Mitigation direction
- Inventory Publify instances and identify versions v8.0 through v9.2.4.
- Update to a Publify release that includes the referenced fix commit.
- If patching is delayed, restrict publisher role access to trusted users only.
- Review recently created pages and articles for suspicious embedded script behavior.
- Check vendor guidance for any additional remediation or upgrade notes.
Validation and detection
- Confirm the running Publify version is outside the affected range.
- Verify the referenced security fix is present in deployed code.
- Review publisher-role accounts and remove unnecessary access.
- Perform authenticated editor sanitization testing in staging without executing scripts.
- Check logs and content history for unexpected page or article modifications.
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 lookupCVE-2021-25974 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://github.com/publify/publify/commit/fefd5f76302adcc425b2b6e7e7d23587cfc0083eCVE reference · x_refsource_MISC
- https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25974CVE 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.