WordPress vulnerability research

Protected vulnerabilities.

Review the attack behind each advisory and the BitFire control—bot protection, WAF, or runtime RASP—that prevents it from becoming a compromise.

Verified-client bot controls Behavior-based WAF Runtime RASP enforcement
Advisory library

How BitFire stops known vulnerabilities

Showing 43–44 of 44 records · Updated September 29, 2026

Critical
CVE-2024-1981

WPvivid

CVSS9.8

WPvivid exposed its staging workflow to unauthenticated requests and used the attacker-controlled table prefix in database statements, while BitFire blocks automated exploit requests, detects SQL injection, and protects sensitive database outcomes.

Affected sites
900,000+
Attack class
SQL Injection
BitFire protectionProtected by BitFire Bot Protection + WAF
Read technical analysis
Critical
CVE-2024-1071

Ultimate Member

CVSS9.8

Ultimate Member lets an unauthenticated visitor inject SQL through its member-directory sorting parameter, while BitFire WAF inspects that input and rejects SQL keywords and evasion signatures before the plugin builds the query.

Affected sites
200,000+
Attack class
SQL Injection
BitFire protectionProtected by BitFire WAF
Read technical analysis

Page 8 of 8

Protect your WordPress website

Stop the operation, not only the signature.

BitFire combines bot controls, request inspection, and runtime enforcement so emerging vulnerabilities fail before a CVE-specific rule exists.

Protect my site free →