CVE-2026-39371: CWE-352: Cross-Site Request Forgery (CSRF) in redwoodjs sdk
A Cross-Site Request Forgery (CSRF) vulnerability exists in RedwoodJS SDK versions from 1. 0. 0-beta. 50 up to but not including 1. 0. 6. Server functions exported from "use server" files could be invoked via GET requests, bypassing intended HTTP method restrictions. In cookie-authenticated applications, this allowed cross-site GET navigations to trigger state-changing functions due to browsers sending SameSite=Lax cookies on top-level GET requests. This affects all server functions, including serverAction() handlers and bare exported functions. The vulnerability is fixed in version 1.
AI Analysis
Technical Summary
RedwoodJS SDK versions >= 1.0.0-beta.50 and < 1.0.6 have a CSRF vulnerability (CWE-352) because server functions exported from "use server" files can be invoked via GET requests, which bypasses the intended HTTP method restrictions. This allows cross-site GET requests to trigger state-changing server functions in cookie-authenticated applications, leveraging the browser behavior of sending SameSite=Lax cookies on top-level GET navigations. The issue affects all server functions, including serverAction() handlers and other exported functions. The vulnerability has a CVSS 3.1 score of 8.1 (high severity) and was fixed in RedwoodJS SDK version 1.0.6.
Potential Impact
An attacker can cause a victim's browser to perform unintended state-changing actions on a vulnerable RedwoodJS application by tricking the user into visiting a malicious link or page. This occurs because server functions can be invoked via GET requests, and browsers send authentication cookies on these requests, enabling CSRF attacks. The impact includes high integrity and availability consequences, as indicated by the CVSS vector (I:H, A:H). There is no confirmed exploitation in the wild as of the published date.
Mitigation Recommendations
Upgrade RedwoodJS SDK to version 1.0.6 or later, where this vulnerability is fixed. No other mitigation is specified or required according to the available data. Patch status is confirmed by the vendor's versioning information.
CVE-2026-39371: CWE-352: Cross-Site Request Forgery (CSRF) in redwoodjs sdk
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in RedwoodJS SDK versions from 1. 0. 0-beta. 50 up to but not including 1. 0. 6. Server functions exported from "use server" files could be invoked via GET requests, bypassing intended HTTP method restrictions. In cookie-authenticated applications, this allowed cross-site GET navigations to trigger state-changing functions due to browsers sending SameSite=Lax cookies on top-level GET requests. This affects all server functions, including serverAction() handlers and bare exported functions. The vulnerability is fixed in version 1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RedwoodJS SDK versions >= 1.0.0-beta.50 and < 1.0.6 have a CSRF vulnerability (CWE-352) because server functions exported from "use server" files can be invoked via GET requests, which bypasses the intended HTTP method restrictions. This allows cross-site GET requests to trigger state-changing server functions in cookie-authenticated applications, leveraging the browser behavior of sending SameSite=Lax cookies on top-level GET navigations. The issue affects all server functions, including serverAction() handlers and other exported functions. The vulnerability has a CVSS 3.1 score of 8.1 (high severity) and was fixed in RedwoodJS SDK version 1.0.6.
Potential Impact
An attacker can cause a victim's browser to perform unintended state-changing actions on a vulnerable RedwoodJS application by tricking the user into visiting a malicious link or page. This occurs because server functions can be invoked via GET requests, and browsers send authentication cookies on these requests, enabling CSRF attacks. The impact includes high integrity and availability consequences, as indicated by the CVSS vector (I:H, A:H). There is no confirmed exploitation in the wild as of the published date.
Mitigation Recommendations
Upgrade RedwoodJS SDK to version 1.0.6 or later, where this vulnerability is fixed. No other mitigation is specified or required according to the available data. Patch status is confirmed by the vendor's versioning information.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-06T21:29:17.350Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d55f0aaaed68159a5629cc
Added to database: 4/7/2026, 7:46:18 PM
Last enriched: 4/15/2026, 12:39:42 PM
Last updated: 5/22/2026, 9:46:34 PM
Views: 61
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.