CVE-2026-82468

Rodauth before 2.47.0 CSRF Protection Bypass via Content-Type

Published Aug 29, 2026 CVSS 4.0 · 4.9 Medium EPSS < 1% KEV · Not listed
Description
Rodauth before 2.47.0 contains a cross-site request forgery protection bypass vulnerability in the JSON request content type validation. Attackers can craft cross-origin form posts with content types containing application/json substrings to bypass CSRF token validation and force victims to authenticate to attacker-controlled accounts.

Analysis

AI-generated

Technical impact

Rodauth prior to version 2.47.0 contains a CSRF protection bypass that lets attackers craft cross‑origin form posts whose Content‑Type headers include application/json substrings. This bypass skips the CSRF token validation and forces victims to authenticate to attacker‑controlled accounts, resulting in unauthorized access. The weakness is classified as a CSRF flaw (CWE‑352).

Affected Systems

The issue affects all users of the Rodauth authentication library at versions older than 2.47.0. Any deployment that integrates these older versions and accepts form‑based requests with JSON content‑type handling is potentially impacted. The vulnerability is inherent in the library’s request validation logic regardless of the surrounding application code.

Risk and Exploitability

Based on the description, it is inferred that the attack vector is a cross‑origin POST request with a crafted Content‑Type header containing application/json substrings. The CVSS score of 4.9 indicates medium severity, and no EPSS exploitation data is currently available. The vulnerability is not listed in the CISA KEV catalog, suggesting it has not yet been widely abused. Attackers only need to send a crafted cross‑origin POST request; no privileged access to the server is required. The primary risk is potential illicit account takeover by bypassing standard CSRF defenses.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Rodauth to version 2.47.0 or later to apply the official CSRF protection fix.
  • Ensure that the server validates the Content‑Type header for incoming requests, rejecting or normalizing any that contain application/json substrings for form submissions that should be protected by CSRF tokens.
  • Confirm that CSRF token verification is applied to every state‑changing request, including those that use custom wrappers or internal redirects, and enforce same‑origin checks on all form posts.

Generated by OpenCVE AI on August 29, 2026 at 17:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Jeremyevans
Jeremyevans rodauth
Vendors & Products Jeremyevans
Jeremyevans rodauth
Type Values Removed Values Added
Description Rodauth before 2.47.0 contains a cross-site request forgery protection bypass vulnerability in the JSON request content type validation. Attackers can craft cross-origin form posts with content types containing application/json substrings to bypass CSRF token validation and force victims to authenticate to attacker-controlled accounts.
Title Rodauth before 2.47.0 CSRF Protection Bypass via Content-Type
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 4.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N'}

cvssV4_0

{'score': 4.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N'}

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 2, 2026, 6:01 PM
Reserved
Aug 29, 2026, 2:11 PM
Status
Deferred
Published
Aug 29, 2026, 5:17 PM
Modified
Sep 11, 2026, 6:26 PM