CVE-2026-42551: CWE-436: Interpretation Conflict in flightphp core
FlightPHP versions prior to 3.18.1 contain a vulnerability where the Request::getMethod() function unconditionally trusts the X-HTTP-Method-Override header and the $_REQUEST['_method'] parameter for all HTTP verbs, including safe ones like GET. This allows an attacker to change the HTTP method of a request silently, potentially turning a GET request into a DELETE or PUT. This behavior can lead to Cross-Site Request Forgery (CSRF) escalation against destructive endpoints, bypass middleware protections based on HTTP verbs, and cause cache poisoning between CDN and origin. The issue is fixed in version 3.18.1.
AI Analysis
Technical Summary
The vulnerability in FlightPHP core prior to version 3.18.1 arises from the Request::getMethod() method honoring the X-HTTP-Method-Override header and the $_REQUEST['_method'] parameter without any opt-in mechanism or whitelist of allowed methods. This flaw allows any HTTP verb, including safe ones like GET, to be overridden to unsafe methods such as DELETE or PUT. Consequently, this can enable attackers to escalate CSRF attacks against endpoints that perform destructive actions, bypass middleware that restricts unsafe HTTP verbs, and poison caches between CDN and origin servers. The vulnerability is identified as CWE-436 (Interpretation Conflict). It has a CVSS 3.1 score of 7.5 (high severity) with no privileges or user interaction required for exploitation. The vulnerability is fixed in FlightPHP version 3.18.1.
Potential Impact
An attacker can exploit this vulnerability to escalate CSRF attacks by converting safe HTTP requests into unsafe ones (e.g., GET to DELETE or PUT), potentially causing unauthorized destructive actions. Middleware protections that rely on HTTP verb checks can be bypassed, and cache poisoning attacks between CDN and origin servers are possible. There is no confidentiality impact reported, but integrity is highly impacted. Availability is not affected. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade FlightPHP to version 3.18.1 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 3.18.1, applying this official patch is the recommended remediation. No alternative mitigations or temporary fixes are indicated in the available data.
CVE-2026-42551: CWE-436: Interpretation Conflict in flightphp core
Description
FlightPHP versions prior to 3.18.1 contain a vulnerability where the Request::getMethod() function unconditionally trusts the X-HTTP-Method-Override header and the $_REQUEST['_method'] parameter for all HTTP verbs, including safe ones like GET. This allows an attacker to change the HTTP method of a request silently, potentially turning a GET request into a DELETE or PUT. This behavior can lead to Cross-Site Request Forgery (CSRF) escalation against destructive endpoints, bypass middleware protections based on HTTP verbs, and cause cache poisoning between CDN and origin. The issue is fixed in version 3.18.1.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in FlightPHP core prior to version 3.18.1 arises from the Request::getMethod() method honoring the X-HTTP-Method-Override header and the $_REQUEST['_method'] parameter without any opt-in mechanism or whitelist of allowed methods. This flaw allows any HTTP verb, including safe ones like GET, to be overridden to unsafe methods such as DELETE or PUT. Consequently, this can enable attackers to escalate CSRF attacks against endpoints that perform destructive actions, bypass middleware that restricts unsafe HTTP verbs, and poison caches between CDN and origin servers. The vulnerability is identified as CWE-436 (Interpretation Conflict). It has a CVSS 3.1 score of 7.5 (high severity) with no privileges or user interaction required for exploitation. The vulnerability is fixed in FlightPHP version 3.18.1.
Potential Impact
An attacker can exploit this vulnerability to escalate CSRF attacks by converting safe HTTP requests into unsafe ones (e.g., GET to DELETE or PUT), potentially causing unauthorized destructive actions. Middleware protections that rely on HTTP verb checks can be bypassed, and cache poisoning attacks between CDN and origin servers are possible. There is no confidentiality impact reported, but integrity is highly impacted. Availability is not affected. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade FlightPHP to version 3.18.1 or later, where this vulnerability is fixed. Since the vendor advisory confirms the fix in 3.18.1, applying this official patch is the recommended remediation. No alternative mitigations or temporary fixes are indicated in the available data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-28T16:56:50.191Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a04d644cbff5d861003f1fb
Added to database: 05/13/2026, 19:51:32 UTC
Last enriched: 05/21/2026, 12:23:55 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 85
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.