← Back to results
Vulnerability record · public intelligence
CVE-2024-47812
MEDIUM

Cross-site Scripting (XSS) on Special:RequestImportQueue when displaying request date in ImportDump

Published Oct 9, 2024 · Updated Oct 23, 2026

Severity · CVSSMEDIUM · 6.0
Known exploitationNot listed
EPSS / likelihood0.41%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Cross-site Scripting (XSS) on Special:RequestImportQueue when displaying request date in ImportDump

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

ImportDump is an extension for mediawiki designed to automate user import requests. Anyone who can edit the interface strings of a wiki (typically administrators and interface admins) can embed XSS payloads in the messages for dates, and thus XSS anyone who views Special:RequestImportQueue. This issue has been patched in commit `d054b95` and all users are advised to apply this commit to their branch. Users unable to upgrade may either Prevent access to Special:RequestImportQueue on all wikis, except for the global wiki; and If an interface administrator (or equivalent) level protection is available (which is not provided by default) on the global wiki, protect the affected messages up to that level. This causes the XSS to be virtually useless as users with those rights can already edit Javascript pages. Or Prevent access to Special:RequestImportQueue altogether.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. https://issue-tracker.miraheze.org/T12698 ↗

Record history

Published Oct 9, 2024 · Last refreshed Oct 23, 2026