Loading story…
XenForo disclosed and patched three high-severity vulnerabilities affecting multiple 2.2 and 2.3 releases, including remote code execution, OAuth2 authorization abuse, and a template method call restriction bypass. The most severe issue, CVE-2026-35056, allows an authenticated but malicious administrator with admin control panel access to execute arbitrary code on the server, affecting versions before 2.3.9 and 2.2.18. The flaw is classified as CWE-94 and carries a high-impact CVSS vector indicating compromise of confidentiality, integrity, and availability.
Two additional XenForo flaws affect authorization controls in the platform. CVE-2025-71278 impacts versions before 2.3.5 and allows OAuth2 client applications to request unauthorized scopes, potentially granting access beyond intended permissions; it is mapped to CWE-863. CVE-2025-71281 affects versions before 2.3.7 and stems from a loose prefix match in template callback and variable method-call handling, enabling unauthorized method invocation from templates. XenForo addressed the issues in security releases 2.3.5, 2.3.7, 2.3.9, and 2.2.18, with advisories also published by VulnCheck.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
VulnCheck disclosure records for CVE-2025-71278, CVE-2025-71281, and CVE-2026-35056 were newly received on April 1, 2026, documenting the vulnerabilities, affected versions, severity scoring, and references to XenForo security releases.
XenForo released versions 2.2.18 and 2.3.9 to address CVE-2026-35056, a remote code execution vulnerability that allowed an authenticated malicious admin with admin panel access to execute arbitrary code on the server.
XenForo released version 2.3.7 with a security fix for a vulnerability later tracked as CVE-2025-71281. The flaw affected versions before 2.3.7 and stemmed from loose prefix matching for methods callable from templates, enabling unauthorized method invocations.
XenForo released version 2.3.5 with a security fix for an issue later tracked as CVE-2025-71278, which allowed OAuth2 client applications to request unauthorized scopes in XenForo 2.3 versions before 2.3.5.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
XenForo released fixes in version **2.3.7** for two newly disclosed vulnerabilities affecting earlier versions of the forum platform. The more severe issue, tracked as **`CVE-2025-71279`**, is a **CWE-287** authentication weakness involving passkeys added to user accounts that could allow an unauthenticated remote attacker to compromise passkey-based authentication. The flaw carries a **CVSS 3.1** rating of `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, indicating high impact across confidentiality, integrity, and availability. A second flaw, **`CVE-2025-71282`**, is a **CWE-209** information disclosure bug that can expose filesystem paths through exception messages triggered by `open_basedir` restrictions. That issue affects XenForo versions before **2.3.7** and could help attackers map a server's directory structure, with a **CVSS 3.1** vector of `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`. Advisory references and the XenForo release notice indicate that upgrading to **2.3.7** addresses both vulnerabilities.
Jun 29, 2026
Researchers detailed how attackers can abuse improperly exposed "protected" method handling in vBulletin to achieve unauthenticated remote code execution on internet-facing forums. The issue affects vBulletin `5.0.0` through `5.7.5` and `6.0.0` through `6.0.3` running on PHP `8.1` or newer, and is tracked as **CVE-2025-48827** and **CVE-2025-48828**. Technical analysis showed the flaws can be chained from remote access to protected method invocation and full code execution on vulnerable servers. CSIRT.SK reported the vulnerabilities are being actively exploited in the wild, with abuse observed since at least May 2025, while many exposed instances remain unpatched. The vendor had reportedly released fixes in April 2024 without detailed public disclosure, leaving administrators unaware of the severity until later reporting. Defenders are being urged to update affected installations to the recommended patched versions or the latest release and to review server and application logs for evidence of compromise.
Jul 24, 2026
vBulletin disclosed and patched **CVE-2026-61511**, a critical unauthenticated remote code execution flaw in its template engine that can let attackers execute arbitrary PHP code on self-hosted forum servers. The bug affects multiple releases, including **5.x through 5.7.5** and **6.x through 6.2.1** according to advisory coverage, and is fixed in **6.2.2** with patches also issued for supported branches. The vulnerability is rooted in `vB5_Template_Runtime::runMaths()` in `vb5/template/runtime.php`, where insufficient input filtering allows attacker-controlled expressions to reach PHP's `eval()`.
Jul 29, 2026