Skip to main content
VulnerabilityPublished Updated

CVE-2025-11183: QGIS QWC2 · XSS or 'Cross-site Scripting'

Affects QGIS QWC2Source CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/AU:N/RE:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
QGIS QWC2Affected
  • =0
Fixed in–

AI-suggested

  1. Monitor QGIS project communications closely and apply official patches or updates for QWC2 as soon as they become available to address CVE-2025-11183.
  2. Implement strict access controls to QWC2 interfaces, ensuring only trusted and necessary users have authorized access.
  3. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious input patterns targeting attribute tables.
  4. Conduct input validation and output encoding on all user-supplied data within QWC2, especially in attribute tables, to prevent script injection.
  5. Educate users about the risks of interacting with untrusted content within QWC2 and encourage vigilance against phishing or social engineering attempts.
  6. Regularly audit and monitor logs for unusual activity or signs of attempted exploitation.
  7. Consider network segmentation to isolate QGIS servers from broader enterprise networks, reducing lateral movement potential.
  8. If feasible, deploy Content Security Policy (CSP) headers to restrict execution of unauthorized scripts within the QWC2 web client.
  9. Review and tighten privilege assignments to minimize the number of users with write or edit capabilities in attribute tables.

Description

Cross-Site Scripting vulnerability in attribute table in QGIS QWC2 <2025.08.14 allows an authorized attacker to plant arbitrary JavaScript code in the page

References

Community reviews

Loading reviews…