CVE-2025-70810
CSRF in phpBB 3.3.15 Enables Arbitrary Code Execution
Publication date: 2026-04-09
Last updated on: 2026-04-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpbb | phpbb | 3.3.15 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-70810 is a Cross-Site Request Forgery (CSRF) vulnerability in phpBB version 3.3.15 affecting the login functionality.
The issue arises because the login endpoint accepts POST requests without enforcing robust CSRF protection mechanisms that are properly bound to the user session during authentication.
This allows an attacker to craft a malicious webpage that, when visited by a victim, causes the victimβs browser to submit a forged login request.
Consequently, the victimβs session may become authenticated under attacker-controlled credentials, leading to session confusion and account context manipulation.
The vulnerability does not directly expose user credentials but can result in unintended session states and potential misuse of authenticated session workflows.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to manipulate your session authentication state.
An attacker can cause your browser to log in with attacker-supplied credentials without your knowledge, leading to session confusion.
This may result in unauthorized actions being performed under your session or misuse of authenticated workflows.
However, it does not directly expose your user credentials.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unauthorized or forged POST requests to the phpBB login endpoint that lack proper CSRF tokens or have suspicious Origin and Referer headers.
One way to detect exploitation attempts is to capture and analyze HTTP traffic targeting the login function of phpBB 3.3.15, looking for POST requests that do not include valid CSRF tokens or have unusual session behaviors.
Suggested commands include using network traffic analysis tools such as tcpdump or tshark to filter HTTP POST requests to the login URL, for example:
- tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'POST /ucp.php?mode=login'
- tshark -Y 'http.request.method == "POST" && http.request.uri contains "login"' -T fields -e http.host -e http.request.uri -e http.cookie -e http.referer
Additionally, reviewing web server logs for POST requests to the login endpoint without accompanying CSRF tokens or with suspicious Referer headers can help identify potential exploitation.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include enforcing CSRF protection on authentication requests by implementing CSRF tokens that are strictly bound to user sessions.
Additional measures include setting the SameSite attribute on cookies to Lax or Strict to prevent cross-site requests from being accepted.
Validating the Origin and Referer headers on login requests to ensure they originate from trusted sources is also recommended.
If possible, update phpBB to a version where this vulnerability is patched or apply vendor-provided patches.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows an attacker to manipulate authenticated sessions via Cross-Site Request Forgery (CSRF) on the login function, potentially leading to session confusion and misuse of authenticated workflows.
While the vulnerability does not directly expose user credentials or personal data, the ability to manipulate session states could indirectly impact the security and integrity of user data.
This could have implications for compliance with standards like GDPR and HIPAA, which require protection of user data and secure authentication mechanisms to prevent unauthorized access.
Failure to mitigate such vulnerabilities might lead to unauthorized actions within user sessions, potentially violating requirements for data confidentiality and integrity under these regulations.