Security readout for executives and security teams
Plain-English summary
PageKit v1.0.18 may allow CMS users to upload SVG files containing scripts. If a visitor clicks a link to that uploaded file, the script can run in the visitor's browser, creating an XSS risk. The sources do not provide a CVSS score, fixed version, or confirmed exploitation.
Executive priority
Treat this as a targeted web application risk, not a confirmed emergency. Prioritize if PageKit v1.0.18 is internet-facing, allows multiple CMS uploaders, or hosts sensitive user sessions.
Technical view
The issue is an upload handling weakness in PageKit v1.0.18. SVG content uploaded through the CMS file upload flow is reportedly not stripped or filtered, and the stored file can be served from the storage path. When accessed by a user, embedded script may execute as cross-site scripting.
Likely exposure
Exposure is likely limited to PageKit v1.0.18 sites where CMS users can upload SVG files and those uploads are publicly reachable from the site storage path.
Exploitation context
The bundle references a public GitHub issue and marks KEV as false. There is no cited evidence of active exploitation, exploit tooling, or weaponized campaigns. The described attack requires an uploaded malicious SVG and a victim accessing it.
Researcher notes
The evidence is narrow: PageKit v1.0.18, SVG upload, no filtering, public storage access, and XSS on user access. No CWE, CVSS, patch version, or exploitation evidence is included in the bundle.
Mitigation direction
- Check PageKit vendor guidance; the sources do not name a fixed version.
- Restrict SVG uploads for CMS users until vendor guidance is confirmed.
- Remove or quarantine untrusted SVG uploads from public storage.
- If SVG support is required, validate safe filtering and browser handling.
- Review site CSP and uploaded-file serving behavior as compensating controls.
Validation and detection
- Inventory PageKit deployments and confirm whether v1.0.18 is in use.
- Review CMS upload settings to see whether SVG files are allowed.
- Check public storage paths for existing uploaded SVG files.
- Confirm uploaded SVGs are filtered, blocked, or served safely.
- Review access roles for users who can upload CMS files.
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.
File 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-32245 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/pagekit/pagekit/issues/963CVE 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.