Loading story…
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.
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.
CSIRT.SK published an alert describing CVE-2025-48827 and CVE-2025-48828 as critical, actively exploited vulnerabilities in vBulletin. The advisory urged administrators to update to fixed versions and review logs for signs of compromise.
CSIRT.SK reported that the critical vBulletin vulnerabilities CVE-2025-48827 and CVE-2025-48828 have been actively exploited since at least May 2025. The bugs allow unauthenticated remote exploitation on vulnerable installations running PHP 8.1 or newer, including remote code execution.
The vendor reportedly released updates in April 2024 that addressed what were later identified as CVE-2025-48827 and CVE-2025-48828, but did so without detailed public disclosure. The flaws affected vBulletin 5.0.0 through 5.7.5 and 6.0.0 through 6.0.3.
A technical write-up dissecting an N-day remote code execution issue in vBulletin was published, focusing on abuse of a supposedly protected method. The analysis documented the vulnerability mechanics and exploitation path.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map 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.
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
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.
Jun 29, 2026
Craft CMS disclosed and patched two **critical** vulnerabilities, `CVE-2025-32432` and `CVE-2024-58136`, that can be chained or abused to achieve **unauthenticated remote code execution** and full compromise of vulnerable servers. The flaws affect Craft CMS `5.x` before `5.6.17`, `4.x` before `4.14.15`, and `3.x` before `3.9.15`; one issue involves insufficient input validation in image transformation functionality, while the other stems from unsafe handling of the `__class` variable in the underlying Yii 2 framework. Researchers and national defenders reported that the vulnerabilities are being **actively exploited in the wild**, with investigations tying attacks to malicious requests targeting the `actions/assets/generate-transform` endpoint and abuse of `__class` parameters. Organizations running exposed Craft CMS instances were urged to patch immediately, review logs for suspicious POST activity, check file and system integrity, and rotate credentials if compromise is suspected.
Jul 24, 2026