home / blog
2026-11-10 · critical
CVE-2026-61511: Unauthenticated RCE in vBulletin 5.x-6.x
Unauthenticated RCE in vBulletin via eval injection in template runtime.

CVE-2026-61511 describes an eval injection vulnerability in the vB5_Template_Runtime::runMaths() method of vBulletin. The flaw lies in insufficiently restrictive input filtering, specifically in the pagenav[pagenumber] parameter processed by the unauthenticated ajax/render template route. Unauthenticated remote attackers can exploit this weakness to inject and execute arbitrary PHP code on the server.
The vulnerability has critical severity with a CVSS score of 9.8. According to official NVD data from July 27, 2026, affected versions are vBulletin 5.x through 5.7.5 and 6.x through 6.2.1. Signals observed on social platforms in the last 24 hours indicate growing awareness of the flaw within the security community. The lack of authentication protection makes the flaw accessible to anyone, further increasing the risk.
System administrators managing vBulletin must update immediately to versions prior to 5.7.5 (for 5.x branch) or 6.2.1 (for 6.x branch). If updates are not immediately feasible, it is essential to restrict access to the ajax/render template route via application firewall or web application firewall (WAF), blocking requests with suspicious parameters in pagenav. Logging and monitoring for eval injection patterns must be activated immediately.
At a glance
- What
- Eval injection in vB5_Template_Runtime::runMaths() enabling unauthenticated RCE via insufficiently restrictive regex in pagenav[pagenumber] parameter of unauthenticated ajax/render template route
- Severity
- Critical, CVSS 9.8 - unauthenticated RCE with immediate impact and direct exploitation without credentials
- Affected versions
- vBulletin 5.x through 5.7.5 and 6.x through 6.2.1
- Fix
- Update vBulletin to versions after 5.7.5 (5.x branch) or after 6.2.1 (6.x branch). No partial patches or alternative mitigations are listed in official NVD documentation.
- Status
- Officially published July 27, 2026. Signals observed on social media in the last 24 hours indicate growing awareness within the security community.
- Action
- 1) Immediately verify vBulletin versions in use. 2) Plan updates as urgent. 3) If updates are not immediate, implement firewall restrictions on ajax/render route. 4) Monitor access logs and PHP errors for eval injection patterns.
Sources: NVD, CVE-2026-61511