CVE-2026-54263

Wagtail: Reflected XSS in dynamic image URL generator view

from django.http import HttpResponseBadRequest
from django.urls import path
from wagtail.admin import urls as wagtailadmin_urls

def disabled_output(request, image_id):
    return HttpResponseBadRequest("", content_type="text/plain")

urlpatterns = [
    # Example where the CMS admin is at /admin/.
    # Add this before the Wagtail admin URLs registration, with the same sub-path.
    path("admin/images/<int:image_id>/generate_url/output/", disabled_output),
    path("admin/", include(wagtailadmin_urls)),
]

A reflected cross-site scripting (XSS) vulnerability exists on the dynamic image URL generator view within the Wagtail admin interface. A user with a limited-permission editor account for the Wagtail admin could craft a URL that, when viewed by a user with higher privileges, could perform actions with that user's credentials. The vulnerability is present for all sites, even if they do not enable the dynamic image serve view. The vulnerability is not exploitable by an ordinary site visitor without access to the Wagtail admin.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-54263 has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.3.3, 7.4.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched versions have been released as Wagtail 7.3.3 and 7.4.2.

1. What is CVE-2026-54263? CVE-2026-54263 is a high-severity cross-site scripting (XSS) vulnerability in wagtail (pip), affecting versions >= 7.3, < 7.3.3. It is fixed in 7.3.3, 7.4.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2026-54263? CVE-2026-54263 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of wagtail are affected by CVE-2026-54263? wagtail (pip) versions >= 7.3, < 7.3.3 is affected.
4. Is there a fix for CVE-2026-54263? Yes. CVE-2026-54263 is fixed in 7.3.3, 7.4.2. Upgrade to this version or later.
5. Is CVE-2026-54263 exploitable, and should I be worried? Whether CVE-2026-54263 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-54263 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-54263?
   • Upgrade wagtail to 7.3.3 or later
   • Upgrade wagtail to 7.4.2 or later

Other vulnerabilities in wagtail