Read the docs
TI-2022-15847 Aliases CVE-2022-35118GHSA-9725-wqpv-8rxj

PyroCMS v3.9 was discovered to contain multiple cross-site scripting (XSS) vulnerabilities.

Priority LOW 28CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-79.

Summary

PyroCMS v3.9 was discovered to contain multiple cross-site scripting (XSS) vulnerabilities.

Why it matters now

EPSS 0.00526 44th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:pyrocms:pyrocms:*:*:*:*:*:*:*:*up to 3.9VulnerablePyrocms
  • cpe:2.3:a:pyrocms:pyrocms:*:*:*:*:*:*:*:* Versions up to 3.9 Vulnerable ·Pyrocms

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-35118
  2. 2026-10-03 Alias added: GHSA-9725-wqpv-8rxj

References

Advisory 1

  • TI-2023-13964 PyroCMS 3.9 contains a remote code execution (RCE) vulnerability that can be exploited… CVSS 3.1CRITICAL 9.8
  • TI-2024-38394 PyroCMS v3.0.1 Stored Cross-Site Scripting via Admin Redirects CVSS 4.0MEDIUM 5.3
  • TI-2022-17541 PyroCMS 3.9 is vulnerable to a stored Cross Site Scripting (XSS_ when a low privileged… CVSS 3.1CRITICAL 9.0
  • TI-2020-15498 PyroCMS 3.7 is vulnerable to cross-site request forgery (CSRF) via the… CVSS 3.1HIGH 7.1
  • TI-2020-15497 PyroCMS 3.7 is vulnerable to cross-site request forgery (CSRF) via the admin/pages/delete/ URI: pages will be deleted. CVSS 3.1MEDIUM 4.3

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences