Stored XSS via unsanitized Wiki content fields
Published Jul 5, 2024 · Updated Nov 4, 2025
Stored XSS in drupal-wiki.com Drupal Wiki before 8.31.1 allows remote attackers to execute JavaScript in visitors' browsers. Wiki comments, captions, and image titles preserve attacker-supplied event-handler markup and render it when a visitor opens the page. Exploitation requires permission to comment on or edit a Wiki page and a visitor who subsequently views the stored content.
Summary
What happened
Stored XSS in drupal-wiki.com Drupal Wiki before 8.31.1 allows remote attackers to execute JavaScript in visitors' browsers. Wiki comments, captions, and image titles preserve attacker-supplied event-handler markup and render it when a visitor opens the page. Exploitation requires permission to comment on or edit a Wiki page and a visitor who subsequently views the stored content.
The record
- CVE
- CVE-2024-34481
- Published
- Jul 5, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 5, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Drupal Wiki persistent XSS proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo