GHSA-v853-p72q-4cfw: CSRF

Published Oct 5, 2026
·
Updated

Summary Quart 0.23.0 contains a stray debug statement (print(data)) inside Body.await in quart/wrappers/request.py. Any request whose body is awaited — await request.form, await request.getdata(), WTForms validateonsubmit(), etc. — has its raw, unparsed body printed to stdout, including plaintext form fields such as passwords and CSRF tokens. Confirmed present in 0.23.0, confirmed absent in 0.22.0.

Details In src/quart/wrappers/request.py, Body.await accumulates the request body into a bytearray:

​python data = bytearray() while not self.queue.empty(): data.extend(self.queue.getnowait()) print(data) # <-- not present in 0.22.0 if ( self.maxcontentlength is not None and len(data) > self.maxcontentlength ): raise RequestEntityTooLarge() ​

This fires for every request that awaits its body — the overwhelming majority of POST/PUT routes in a typical Quart app (form submissions, JSON APIs via request.getjson(), file uploads, etc.).

PoC 1. pip install quart==0.23.0 (requires Python 3.13+) 2. Minimal route: ​python @app.route("/login", methods=["POST"]) async def login(): formdata = await request.form ... ​ 3. Submit a POST with form data, e.g. a login form with staffid/password fields. 4. Observe stdout: the full raw body is printed as bytearray(b'csrftoken=...&staffid=...&password=...').

Confirmed via source diff against 0.22.0's request.py, where this line does not exist.

Impact Any app that captures stdout in logs (terminal redirect, systemd/journald, Docker logs, cloud log aggregation, etc.) will have every submitted form body — including login credentials — written to logs in plaintext. This affects any Quart 0.23.0 app handling authentication or any sensitive form data, and is trivially triggerable by any user simply submitting a form (no attacker action required beyond normal use).

Affected Software

1 affected componentFixes available
pip/quart=0.23.0
0.23.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/quart to a version that resolves this vulnerability.

    Fixed in 0.23.1
  2. Upgrade

    Upgrade Quart to a version that resolves this vulnerability.

    Fixed in 0.22.0

Event History

Oct 5, 2026
Advisory Published
via GitHub·10:49 PM
Data Sourced
via GitHub·10:49 PM
DescriptionSeverityWeaknessAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203