Hubzilla 11.2.1 contains a cross-site request forgery vulnerability in the OAuth2 /authorize endpoint handled by Zotlabs\Module\Authorize::post()… (CVE-2026-70556)
Hubzilla 11.2.1 contains a cross-site request forgery vulnerability in the OAuth2 /authorize endpoint handled by Zotlabs\Module\Authorize::post() that allows unauthenticated attackers to register arbitrary OAuth2 applications under an authenticated user's account by submitting a cross-origin POST request without CSRF token or Origin/Referer validation. Attackers can craft a malicious HTML form that autosubmits attacker-chosen OAuth2 parameters including client_id, client_secret, redirect_uri, and scope to silently register a persistent OAuth2 application, enabling interception of future OAuth2 authorization codes when the victim later authenticates against the attacker-controlled client.
AI Analysis
Technical Summary
The vulnerability in Hubzilla 11.2.1 resides in the OAuth2 /authorize endpoint handled by Zotlabs\Module\Authorize::post(). Due to missing CSRF token verification and lack of Origin/Referer header validation, attackers can perform cross-site request forgery attacks. This allows them to silently register OAuth2 applications under the victim's account by submitting attacker-chosen parameters such as client_id, client_secret, redirect_uri, and scope. The persistent OAuth2 application created can intercept authorization codes when the victim later authenticates, posing a risk to OAuth2 authorization integrity.
Potential Impact
An attacker can register arbitrary OAuth2 applications under an authenticated user's account without their consent. This can lead to interception of OAuth2 authorization codes issued to the victim, potentially compromising OAuth2 authorization flows. However, the vulnerability does not directly disclose user data or allow privilege escalation. The CVSS score of 4.3 reflects a moderate impact primarily on integrity.
Mitigation Recommendations
No official patch or remediation information is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should be cautious about cross-origin requests and consider implementing additional CSRF protections or monitoring OAuth2 application registrations if possible.
Hubzilla 11.2.1 contains a cross-site request forgery vulnerability in the OAuth2 /authorize endpoint handled by Zotlabs\Module\Authorize::post()… (CVE-2026-70556)
Description
Hubzilla 11.2.1 contains a cross-site request forgery vulnerability in the OAuth2 /authorize endpoint handled by Zotlabs\Module\Authorize::post() that allows unauthenticated attackers to register arbitrary OAuth2 applications under an authenticated user's account by submitting a cross-origin POST request without CSRF token or Origin/Referer validation. Attackers can craft a malicious HTML form that autosubmits attacker-chosen OAuth2 parameters including client_id, client_secret, redirect_uri, and scope to silently register a persistent OAuth2 application, enabling interception of future OAuth2 authorization codes when the victim later authenticates against the attacker-controlled client.
CVSS v3.1
Score 4.3medium
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 Hubzilla 11.2.1 resides in the OAuth2 /authorize endpoint handled by Zotlabs\Module\Authorize::post(). Due to missing CSRF token verification and lack of Origin/Referer header validation, attackers can perform cross-site request forgery attacks. This allows them to silently register OAuth2 applications under the victim's account by submitting attacker-chosen parameters such as client_id, client_secret, redirect_uri, and scope. The persistent OAuth2 application created can intercept authorization codes when the victim later authenticates, posing a risk to OAuth2 authorization integrity.
Potential Impact
An attacker can register arbitrary OAuth2 applications under an authenticated user's account without their consent. This can lead to interception of OAuth2 authorization codes issued to the victim, potentially compromising OAuth2 authorization flows. However, the vulnerability does not directly disclose user data or allow privilege escalation. The CVSS score of 4.3 reflects a moderate impact primarily on integrity.
Mitigation Recommendations
No official patch or remediation information is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should be cautious about cross-origin requests and consider implementing additional CSRF protections or monitoring OAuth2 application registrations if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q8qh-69f5-v25q
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-70556"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a74cf7cbf8831d5391acb26
Added to database: 08/06/2026, 18:16:28 UTC
Last enriched: 08/06/2026, 18:24:44 UTC
Last updated: 08/07/2026, 00:56:14 UTC
Views: 3
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.
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.