Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) is an attack that forces an authenticated user to execute unwanted actions on a web application. CSRF attacks target state-changing requests — not data theft — since the attacker cannot see the response to the forged request.
CSRF exploits the browser's automatic inclusion of credentials (cookies, HTTP auth) with every request to a domain. If a user is logged into a banking site and visits a malicious page, that page can submit a hidden form to the banking site — and the browser will attach the user's session cookie automatically. The impact ranges from changing email addresses and passwords to transferring funds and modifying account settings.
While SameSite cookie attributes and CSRF tokens have significantly reduced the attack surface, bypasses continue to emerge. Common techniques include exploiting misconfigured SameSite policies, token fixation, subdomain takeover to bypass origin checks, and leveraging CORS misconfigurations. JSON-based CSRF using Flash or content-type tricks has historically been a rich area for bypasses, and new browser behaviors regularly shift what's exploitable.
CSRF is often combined with other vulnerabilities — an XSS bug can extract CSRF tokens, and open redirects can be used to leak tokens through the Referer header.
This page collects CSRF research, bypass techniques, defense mechanisms, and real-world writeups demonstrating exploitation in modern applications.
From OWASP
SameSite changed the odds; it did not end the class
Cross-site request forgery used to be near-universal and is now genuinely
uncommon, because browsers changed the default. With SameSite=Lax
applied to cookies that do not specify otherwise, the classic silent
cross-origin POST no longer carries the victim's session. That is a real
structural fix, and it means CSRF findings today tend to come from the places
the default does not reach.
Those places are worth listing, because they are where the current research
sits. Lax permits top-level GET navigation, so a state-changing
action reachable by GET is still exploitable — and applications that route
everything through a framework often have more GET-triggered side effects than
their developers believe. Some browsers apply a short window during which a
newly issued cookie behaves as None. Cookies explicitly set to
SameSite=None for legitimate cross-site integrations are back to
the old behaviour entirely. And any authentication that is not cookie-based —
a token attached by JavaScript, or HTTP Basic — was never covered by SameSite
in the first place.
Token implementations fail in recognizable ways, and a good portion of the writeups here are about those: a token that is validated only when present, so removing the parameter passes; a token checked for length rather than value; a token shared across a whole user population rather than bound to a session; validation that applies to POST but not to an equivalent PUT or DELETE; a token accepted from a different user's session. Method override headers and parameters quietly reintroduce the problem where a framework honours them.
CSRF also interacts with CORS in a way that causes persistent confusion. A permissive CORS policy does not cause CSRF — CSRF works without reading the response — but a reflected origin with credentials allowed is a related and usually more severe bug. Several entries below cover both, and testing them together is the efficient way to work.
| Date Added | Link | Excerpt |
|---|---|---|
| 2026-11-19 NEW 2026 | OpenText Vibe CSRF token exposure news | OpenText Vibe versions up to and including 4.0.8.7 are affected by a Cross-Site Request Forgery (CSRF) vulnerability. This weakness allows an attacker to trick a user into performing an unwanted action on the Vibe application without their knowledge or consent. The core issue lies in the exposure of CSRF tokens, which are meant to protect against such attacks. Attackers can exploit this exposure to potentially compromise user sessions or data. |
| 2026-11-19 NEW 2026 | Edwiser Bridge WordPress REST CSRF/scope flaw news | Edwiser Bridge WordPress plugin, versions prior to 4.3.5, contain a critical Cross-Site Request Forgery (CSRF) vulnerability. This flaw exists within the plugin's REST API, specifically affecting the scope of the API endpoints. Attackers can exploit this vulnerability to perform unauthorized actions on behalf of authenticated users, potentially leading to data manipulation or compromise. Updating to version 4.3.5 or later is crucial to patch this security weakness. |
| 2026-11-19 NEW 2026 | ICRTouch ByTable wallet top-up CSRF intermediate | A cross-site request forgery (CSRF) vulnerability has been discovered in ICRTouch's ByTable wallet top-up feature. This allows an attacker to trick a user into unintentionally topping up their wallet using malicious web pages, emails, or messages. The vulnerability exploits a weakness in how the application handles requests, enabling unauthorized transactions without the user's knowledge or consent. |
| 2026-11-19 NEW 2026 | Samsung Health CSRF intermediate Mobile | A cross-site request forgery (CSRF) vulnerability has been identified in Samsung Health, affecting versions prior to a specific update. This flaw could allow attackers to trick users into performing unintended actions within the Samsung Health application without their explicit consent. The vulnerability could be exploited through specially crafted web pages or links. Users are advised to update their Samsung Health application to the latest version to patch this security issue. |
| 2026-11-19 NEW 2026 | ICRTouch ByTable/TouchTakeaway missing anti-CSRF intermediate | ICRTouch's ByTable and TouchTakeaway applications are vulnerable to Cross-Site Request Forgery (CSRF) attacks due to a lack of consistent anti-CSRF measures. This means attackers could trick users into executing unwanted actions on the application without their knowledge. |
| 2026-11-18 NEW 2026 | XE-1545: Agent note and patch-ref routes never check CSRF news 2 min read Bug Bounty | Writeup of XE-1545 details a CSRF vulnerability in the XE Network bounty desk. The `/v1/tickets/{id}/notes` and `/v1/tickets/{id}/patch-refs` routes, when accessed via the team session cookie, bypass CSRF protection. This validation gap, while mitigated by `SameSite=Lax`, could allow an attacker to forge internal notes or patch-reference disclosures attributed to a reviewer, impacting the integrity of "what is fixed" information. The vulnerability was identified by analyzing `desk/api/agent.py` and `desk/static/desk.js`. |
| 2026-11-18 NEW 2026 | Login CSRF via a replayable OAuth code (static state, no PKCE) intermediate 4 min read AuthN Bug Bounty | Writeup detailing a login CSRF vulnerability where a replayable OAuth code, lacking a static state, PKCE, and proper session binding, allowed an attacker to log a victim's browser into an attacker-controlled account. The vulnerability was discovered by observing a fixed "state" parameter and the absence of PKCE during authorization requests. Remediation involves implementing per-request state, enforcing PKCE, binding code consumption to the initiating browser session, and correctly enforcing CSRF tokens. |
| 2026-11-18 NEW 2026 | OAuth-based CSRF: exploiting a flawed state parameter intermediate 5 min read AuthN | Writeup detailing an OAuth-based CSRF vulnerability caused by a flawed state parameter implementation. The analysis highlights how a predictable, non-session-bound state value, incorrectly used as a CSRF defense, allowed for account takeover through crafted links, demonstrating the critical need for cryptographically random, session-bound state parameters in OAuth flows. |
| 2026-11-18 NEW 2026 | CSRF in Brainstorm Force ZIP AI news AI | A Cross-Site Request Forgery (CSRF) vulnerability has been identified in the Brainstorm Force ZIP AI plugin for WordPress. This flaw allows an attacker to trick a logged-in user into submitting a malicious request without their knowledge. The vulnerability is present in the `update_ai_setting` function, specifically when handling the `zip_ai_openai_api_key` parameter. Successful exploitation could lead to unauthorized changes to the plugin's settings. |
| 2026-11-18 NEW 2026 | NamelessMC: OAuth callback state not validated, login CSRF news 3 min read AuthN | Writeup of NamelessMC's OAuth login CSRF vulnerability, GHSA-pmpw-2xvh-5xj6, detailing how the absence of server-side state validation in the OAuth callback flow enables attackers to perform session swapping. By crafting a malicious callback URL and tricking a victim into visiting it, an attacker can force the victim's active session into logging into an attacker-linked NamelessMC account, leading to authentication integrity failures and potential misuse of the victim's session. |
| 2026-11-17 NEW 2026 | Backend Security: JWT, CSRF va SQL Injection qanday ishlaydi?(2) beginner SQLi | This content discusses backend security concepts, specifically focusing on how JWT, CSRF, and SQL injection function. It introduces rate limiting as a method to protect APIs from excessive requests, preventing potential abuse or overload by limiting the number of requests a user can send. The discussion is part of a larger series, indicated by "(2)". |
| 2026-11-17 NEW 2026 | SourceHut disabled registration bypass via login CSRF token (CVE-2026-121728) news 3 min read AuthN | Writeup of CVE-2026-121728, a SourceHut registration bypass via login CSRF token. During a frontend to Go API refactor, a logic bug allowed account creation by submitting the `/register/step2` form, even when registration was disabled. Exploitation required reusing the CSRF token obtained from the `/login` endpoint, as no registration form displayed a unique token. Affected versions span 0.56.11 through 0.88.9. |
| 2026-11-17 NEW 2026 | Keystatic login CSRF news AuthN | Advisory for CVE-2026-129945 detailing a login cross-site request forgery vulnerability in Keystatic through 0.6.9. The githubOauthCallback handler fails to validate the state parameter, allowing unauthenticated attackers to trick victims into signing in with an attacker-controlled GitHub account. This enables attackers to commit victim edits under their own identity by exploiting the missing state validation. |
| 2026-11-17 NEW 2026 | visualTicket CSRF across multiple endpoints news | Library of code and configurations to detect and mitigate Cross-Site Request Forgery (CSRF) vulnerabilities. This entry details how visualTicket's state-changing operations, exposed via GET requests without protection, allow attackers to trick authenticated users into performing unintended actions. It mentions partial remediation in version 20260817, including POST requests for sensitive operations, CSRF tokens, and the `SameSite=Lax` cookie attribute. |
| 2026-11-17 NEW 2026 | emlog pro AI Assistant CSRF to SQL execution PoC news 3 min read AI SQLi | Writeup detailing CVE-2026-73847, a proof-of-concept for emlog pro's AI Assistant CSRF vulnerability. This exploit chains missing CSRF protection, session-cookie-only authentication, and weak confirmation logic to enable an attacker to execute arbitrary SQL against the site database via an admin's authenticated session. The writeup includes techniques for full database reads and writes to all tables except `blog`, demonstrating a complete admin account takeover by overwriting user passwords. Remediation involves adding CSRF token checks, setting `SameSite=Strict` on auth cookies, and implementing per-session confirmation tokens. |
| 2026-11-16 NEW 2026 | Vvveb CSRF intermediate | The Vvveb content management system, up to version 1.0.8.6, has a reported cross-site request forgery (CSRF) vulnerability. This flaw allows an attacker to trick a logged-in user into performing unwanted actions on the Vvveb application without their knowledge. This could potentially lead to unauthorized modifications or other malicious activities by exploiting the user's existing session. |
| 2026-11-16 NEW 2026 | Injection Guard WordPress plugin CSRF intermediate | Library of vulnerabilities for WordPress plugins, detailing the Injection Guard plugin's CSRF flaw (before v1.4.0) that permits unauthenticated password hash export. Attackers can exploit this by tricking administrators into visiting a malicious link, leading to WooCommerce customer email and password hashes being written to an accessible file for offline cracking. |
| 2026-11-15 NEW 2026 | OpenEMR 8.5.0 CSRF in ObservationController intermediate | OpenEMR versions prior to 8.5.0 have a critical cross-site request forgery (CSRF) vulnerability in the ObservationController. This flaw allows attackers to trick authenticated users into performing unintended actions on the system without their knowledge, potentially compromising sensitive patient data or altering medical records. This vulnerability could have significant implications for healthcare providers and their patients. |
| 2026-11-15 NEW 2026 | The bouncer who waves you in with no name tag: Pluck CMS missing-Referer CSRF (CVE-2026-78748) intermediate 4 min read | Writeup detailing CVE-2026-78748 in Pluck CMS, a missing-Referer Cross-Site Request Forgery vulnerability with a CVSS 3.1 score of 8.8. The vulnerability arises because Pluck CMS version 4.7.20's admin panel incorrectly trusts requests when the Referer header is absent, allowing attackers to perform any admin action, including module installation which can lead to remote code execution, by crafting a page that omits the Referer header. |
| 2026-11-15 NEW 2026 | Webmin 2.670 firewalld index.cgi CSRF sets zone to trusted news 6 min read | Analysis of a CSRF vulnerability in Webmin 2.670 affecting the firewalld module. An attacker can exploit a referer-exempt index.cgi script to manipulate firewall-cmd to set the default zone to "trusted" via a crafted link, bypassing SameSite=Lax cookie protections on top-level GET requests. This flaw allows an authenticated user to remotely and silently reconfigure critical firewall settings without further user interaction, as documented by Abraxas Labs. |
| 2026-11-15 NEW 2026 | alchemy_cms: CSRF protection bypassed in admin controllers news | Advisory GHSA-cqh4-xxr9-qc73 details a Cross-Site Request Forgery (CSRF) vulnerability in Alchemy CMS admin controllers, specifically affecting versions 8.4.0 through 8.4.2. The vulnerability arises when `current_user_method` memoizes the user before the CSRF check, allowing attackers to execute state-changing admin actions as a signed-in user by tricking them into visiting a malicious page. Applications employing user memoization, such as those using the Rails 8 authentication generator or `@current_user ||= ...`, are susceptible. |
| 2026-11-15 NEW 2026 | Omnispace Agora Project CSRF news | Writeup detailing GHSA-2wjc-h33p-6wrr, a cross-site request forgery vulnerability in Omnispace Agora Project through 26.10.0. This flaw allows remote attackers to create administrator accounts by exploiting the absence of an anti-CSRF token and insecure cookie handling, enabling privileged actions through forged GET requests. |
| 2026-11-14 NEW 2026 | OpenMage Magento LTS cross-site request forgery (critical) news | Advisory for OpenMage Magento LTS versions before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 detailing a critical cross-site request forgery vulnerability. This flaw in the admin and storefront OAuth confirm and confirmSimple actions allows attackers with OAuth consumer credentials to exploit the lack of form-key validation on GET requests. By tricking a logged-in user into visiting a malicious confirm URL, an attacker can gain a persistent REST API access token bound to the victim. |
| 2026-11-14 NEW 2026 | Apache Roller 5.0.1–6.1.6 CSRF allows unauthenticated attacker actions news | Apache Roller versions 5.0.1 through 6.1.6 are vulnerable to Cross-Site Request Forgery (CSRF). This vulnerability allows an unauthenticated attacker to perform actions on behalf of a logged-in user. The issue stems from insufficient CSRF protection, enabling malicious requests to be executed without proper authorization. This could lead to unauthorized modifications or actions within the application. |
| 2026-11-14 NEW 2026 | Laravel Security: Prevent Mass Assignment, CSRF, and XSS beginner XSS | This content explains how to secure Laravel applications by preventing common vulnerabilities. It focuses on three key areas: * **Mass Assignment:** Using "fillable" properties to explicitly define which attributes can be mass-assigned, preventing unexpected data modifications. * **CSRF (Cross-Site Request Forgery):** Implementing CSRF tokens to ensure requests originate from a legitimate user session. * **XSS (Cross-Site Scripting):** Escaping output within Blade templates to neutralize malicious scripts. These techniques work in tandem to create a robust security posture for Laravel applications. |
| 2026-11-14 NEW 2026 | WriteFreely: CSRF in account settings news | WriteFreely: CSRF in account settings vulnerability allowing attackers to modify user account details, including email, username, blog address, invite links, and published posts. The vulnerability, GHSA-mp2f-3fq8-r9vj, could lead to account takeover if a logged-in user visited a malicious site. Password changes were not affected. Reported by Samyak Jain. |
| 2026-11-14 NEW 2026 | Confirming GraphQL DAST findings: introspection, batching, depth/cost, CSRF over GET intermediate 16 min read API Sec GraphQL | Library for confirming GraphQL DAST findings, detailing how to re-evaluate common scanner reports like introspection enabled, field suggestions, batching, and GET method support. The analysis covers specific techniques for identifying authorization bypasses via mutations like `setRole` and SQL injection through error masking, emphasizing that DAST findings require careful retesting beyond their superficial report. |
| 2026-11-13 2026 | Hono csrf() does not check hyperlink auditing (text/ping) requests intermediate 1 min read | Library vulnerability where Hono's `csrf()` middleware fails to validate requests with `Content-Type: text/ping` originating from Chromium's hyperlink auditing feature. This allows a malicious cross-origin page to trigger state-changing POST requests to an application, bypassing checks for `Origin` and `Sec-Fetch-Site` headers. The vulnerability impacts applications relying solely on `csrf()` for protection, especially for endpoints whose actions are determined by URL paths or query strings rather than the request body. Workarounds include pre-filtering `text/ping` requests or setting session cookies with `SameSite=Strict`. |
| 2026-11-13 2026 | Abilities Bridge WordPress plugin missing nonce CSRF intermediate | The Abilities Bridge WordPress plugin, versions prior to 1.4.2, is vulnerable to Cross-Site Request Forgery (CSRF) due to missing nonces on several administrative functions. This flaw allows unauthenticated users to trick logged-in administrators into performing unintended actions on their behalf. These actions could include modifying plugin settings, potentially leading to unauthorized changes or disruptions to the website. Users are advised to update to version 1.4.2 or later to patch this security vulnerability. |
| 2026-11-13 2026 | webriti vdequator CSRF intermediate | A Cross-Site Request Forgery (CSRF) vulnerability was discovered in webriti vdequator. This flaw allows attackers to trick authenticated users into unknowingly executing unwanted actions on the web application. Exploiting this, an attacker could potentially change settings, delete data, or perform other sensitive operations by submitting malicious requests that the vdequator application would then trust as legitimate. |
| 2026-11-13 2026 | Simple JWT Login WordPress plugin CSRF intermediate JWT | A CSRF vulnerability exists in the Simple JWT Login WordPress plugin. This flaw allows attackers to trick authenticated users into performing unwanted actions without their consent, potentially leading to unauthorized modifications or data exposure. The vulnerability resides in how the plugin handles requests without proper CSRF token validation. Users are advised to update to the latest version of the plugin to mitigate this security risk. |
| 2026-11-13 2026 | social-auth-core login CSRF news AuthN Python | Library documenting GHSA-33vc-vcr3-vj5p, a login CSRF vulnerability in social-auth-core versions before 7.0.0. The SAML backend is affected when RelayState parameters are unsigned, allowing attackers to hijack sessions via an auto-submitting form. This enables users to be signed into attacker-controlled accounts, potentially capturing sensitive data. |
| 2026-11-12 2026 | CSRF vulnerability: a local SameSite cookie experiment beginner | This content describes a Cross-Site Request Forgery (CSRF) vulnerability. This flaw allows a malicious website to trick a logged-in user's browser into sending requests to another site. These requests can alter critical information, like creating a new account or changing existing settings, without the user's explicit consent. The article explores this through a local experiment involving SameSite cookies, a security feature designed to mitigate such attacks. |
| 2026-11-12 2026 | Revive Adserver CSRF in tracker-invocation.php news | Advisory for GHSA-hjwv-982f-254w detailing a cross-site request forgery vulnerability in Revive Adserver 6.0.8 and prior, specifically within `tracker-invocation.php`. This flaw enables attackers to alter tracker names, descriptions, or advertiser assignments by exploiting a state-changing handler that lacks CSRF token verification. Exploitation necessitates victim interaction and a request path containing the victim's session credentials. The vulnerability is resolved in Revive Adserver 6.0.9. |
| 2026-11-12 2026 | SameSite Lax bypass via method override intermediate 3 min read Burp | Writeup detailing a CSRF attack that bypasses Chrome's default `SameSite=Lax` cookie behavior. The vulnerability allows an attacker to change a victim's email address by leveraging the browser's exception for `GET` requests in top-level navigations. The technique involves crafting a link that triggers a top-level `GET` request to the email change endpoint, including a `_method=POST` parameter to override the HTTP method on the server-side, thereby executing the email change without a CSRF token. |
| 2026-11-11 2026 | The CSRF Token Nobody Checked intermediate Bug Bounty | A critical vulnerability discovered in Messenger.com in 2015 allowed any website to impersonate a logged-in user. This was due to the complete absence of Cross-Site Request Forgery (CSRF) token checks. The bug's root cause was this oversight, and its impact was severe, enabling malicious actors to perform actions on behalf of users without their knowledge or consent. The recommended fix involved implementing a default-deny security policy to ensure CSRF tokens are always validated. → masimshahzad.medium.com |
| 2026-11-11 2026 | Action Pack: missing SameSite attribute on session cookies intermediate 1 min read | Advisory GHSA-gmj8-hvj3-49mw details a cross-site request forgery vulnerability in Action Pack's session cookie handling. Non-CookieStore session implementations fail to set the `SameSite` attribute, potentially allowing malicious cross-site requests to carry session cookies in browsers defaulting to `SameSite=Lax`. This impacts API-only applications if actions lack authenticity token verification. Patches and workarounds, such as explicitly configuring `same_site: :lax` during session store setup, are available. |
| 2026-11-11 2026 | ASP.NET Core elevation of privilege via CSRF (CVE-2026-109481) news 2 min read | Advisory for CVE-2026-109481 detailing an ASP.NET Core elevation of privilege vulnerability. Exploitation involves a cross-site request forgery (CSRF) against the /_blazor/refresh path, allowing an attacker to bind a victim's authenticated principal to an attacker-controlled circuit. The vulnerability, with a CVSS score of 7.5, affects Windows, Linux, and macOS platforms across all architectures. Guidance on updating affected applications and components is provided. |
| 2026-11-11 2026 | WPIDE file manager CSRF (high) intermediate | A Cross-Site Request Forgery (CSRF) vulnerability was identified in the WPIDE file manager. This flaw could allow an attacker to trick a logged-in user into performing unwanted actions on their behalf. The vulnerability is categorized as high severity. |
| 2026-11-10 2026 | SAP Web Dispatcher / ICM request forgery (critical) advanced | Advisory for SAP Web Dispatcher and SAP NetWeaver Application Server ABAP (ICM) request forgery, a critical vulnerability. Unauthenticated attackers can exploit insufficient request validation in administrative functions to trick logged-on administrators into visiting malicious links. This can trigger unintended actions within the administrator's session, potentially leading to a full operating system compromise and severe impacts on confidentiality, integrity, and availability. |
| 2026-11-10 2026 | coder: CSRF protection skipped for API paths matching unanchored exemption patterns intermediate 2 min read API Sec | Writeup of GHSA-jvgx-787p-cfmg, a CSRF vulnerability in Coder where unanchored exemption patterns for API paths allowed state-changing requests from same-site pages to bypass CSRF token and same-origin checks. This impacted routes like dev container recreation and user management, with potential exploitation from untrusted workspace apps or shared ports. The vulnerability affected release lines prior to 2.37. |
| 2026-11-10 2026 | Rodauth before 2.47.0 CSRF (CVE-2026-82468) news AuthN | Rodauth versions prior to 2.47.0 are affected by a cross-site request forgery (CSRF) vulnerability (CVE-2026-82468). This flaw allows attackers to trick logged-in users into performing unwanted actions on the application without their knowledge or consent. The vulnerability stems from insufficient validation of certain request parameters. Users are advised to upgrade to Rodauth 2.47.0 or later to mitigate this security risk. |
| 2026-11-10 2026 | Tasmota through 16.0.0 CSRF (high) news | Library for detecting and mitigating Cross-Site Request Forgery (CSRF) vulnerabilities. This library specifically addresses a CSRF flaw in Tasmota versions up to 16.0.0, where attackers could bypass Referer-based protection by manipulating the Referer header to include the device's hostname or IP after a malicious domain. This allows unauthenticated attackers to execute arbitrary console commands and reconfigure settings on vulnerable devices lacking WebPassword protection. |
| 2026-11-10 2026 | SAP NetWeaver Enterprise Portal CSRF intermediate | SAP NetWeaver Enterprise Portal suffers from a Cross-Site Request Forgery (CSRF) vulnerability. This flaw allows unauthenticated attackers to perform actions on behalf of authenticated users, potentially leading to unauthorized changes or data breaches. The vulnerability arises from insufficient validation of HTTP requests. |
| 2026-11-09 2026 | CSRF bug bounty writeups and disclosed reports intermediate Bug Bounty | Writeups cataloging Cross-Site Request Forgery (CSRF) vulnerabilities, detailing 42 reports and analyses from 2024 to 2026. These entries highlight cases where SameSite cookies and tokens were missing, with 27 reports carrying platform-assigned severity, including five rated High or Critical. Each item links to the original disclosure, sourced from platforms like HackerOne. |
| 2026-11-09 2026 | XE-0656: login CSRF signs a victim's browser into an attacker-chosen reporter identity intermediate 3 min read AuthN Bug Bounty | Writeup of XE-0656 details a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the xe.network Desk application, specifically CWE-352, allowing an attacker to sign a victim's browser into an attacker-chosen reporter identity. This occurs because the reporter sign-in mechanism for `xe_login` and OAuth callbacks lacks proper CSRF protection, enabling an attacker to hijack a victim's session, read sealed private reports, and potentially intercept payouts. The report identifies specific code components and suggests fixes including requiring CSRF tokens for `xe_login` and binding OAuth state to the initiating browser. |
| 2026-11-09 2026 | HTTP method override and admin bot exploitation: CSRF lab from a real report intermediate 2 min read Bug Bounty | Lab that recreates a CSRF vulnerability chaining HTTP method override with an admin bot, leading to administrative access and sensitive data exfiltration on a premium car sales platform. This lab mirrors a real-world bug that paid $200 on HackerOne, allowing users to practice this technique within an interactive environment that includes a catalog of vehicles, user management, and a support system processed by an automated bot. The vulnerability stems from the `/api/auth/change-password` endpoint accepting the password change request via both POST and GET methods, enabling a one-click exploit when combined with the admin bot's automatic link processing. |
| 2026-11-09 2026 | Blubrry PowerPress Podcasting CSRF (high) news | A Cross-Site Request Forgery (CSRF) vulnerability has been discovered in Blubrry PowerPress Podcasting, rated as high severity. This flaw could allow attackers to trick authenticated users into performing unintended actions on the website without their knowledge or consent. Exploiting this vulnerability could lead to various malicious activities, impacting user data or site integrity. |
| 2026-11-08 2026 | Apache Juneau CSRF via the content query parameter (CVE-2026-73099) news API Sec | Library for Apache Juneau, fixing CVE-2026-73099, a Cross-Site Request Forgery vulnerability. This flaw occurs when the REST server replaces the request body with a "content" query parameter, enabled by default for all HTTP methods. Attackers can craft cross-site links to inject arbitrary request bodies, bypassing protections that rely on HTTP method or content type. The fix is available in version 9.2.1, or by setting `disableContentParam` to `true`. |
| 2026-11-08 2026 | IBM API Connect CSRF news API Sec | IBM API Connect versions 10.0.8.0 through 10.0.8.12 and 12.1.0.0 are affected by a Cross-Site Request Forgery (CSRF) vulnerability. This flaw allows an attacker to trick authenticated users into performing unintended actions on the API Connect interface. Users should update to the latest secure versions to mitigate this risk. |
Frequently Asked Questions
- What is CSRF and how does it work?
- Cross-Site Request Forgery forces an authenticated user's browser to send an unwanted request to a web application. It exploits the browser's automatic inclusion of cookies with every request to a domain. If a user is logged into Site A and visits a malicious page, that page can submit hidden forms or trigger requests to Site A using the user's session.
- How do SameSite cookies prevent CSRF?
- The SameSite cookie attribute restricts when cookies are sent with cross-origin requests. SameSite=Strict blocks cookies on all cross-site requests. SameSite=Lax (the modern default) allows cookies only for top-level GET navigations, blocking them for POST forms and subresource requests from other origins.
- Is CSRF still relevant with modern frameworks?
- CSRF is less common but not eliminated. SameSite=Lax defaults and framework-level CSRF tokens have reduced the attack surface significantly. However, misconfigurations, subdomain takeover, and APIs that rely on cookie authentication without CSRF tokens remain exploitable. JSON-based CSRF and cross-origin attacks through CORS misconfigurations are active areas of research.
Weekly AppSec Digest
Get new resources delivered every Monday.