What it is
CVE-2026-1581 is an unauthenticated wpForo Forum <= 2.4.14 - Unauthenticated Time-Based SQL Injection.
Vulnerability report
wpForo Forum <= 2.4.14 - Unauthenticated Time-Based SQL Injection
Tomdever / wpForo Forum · * to <= 2.4.14
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2026-1581 is an unauthenticated wpForo Forum <= 2.4.14 - Unauthenticated Time-Based SQL Injection.
Have exploitation attempts been observed?
Yes. Previdian sensors have observed 53 exploitation attempts, 20 unique attacker IPs, and 15 countries targeting CVE-2026-1581. First observed Jun 12, 2026; last observed Nov 12, 2026. Also reported by third-party sources. Confidence is confirmed.
Who is affected?
Tomdever / wpForo Forum * to <= 2.4.14.
What should we do?
Patch immediately, validate internet-facing exposure, and monitor for matching requests.
Overview
The wpForo Forum plugin for WordPress is vulnerable to time-based SQL Injection via the 'wpfob' parameter in all versions up to, and including, 2.4.14 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.
This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
Previdian
Previdian sensors observed exploitation attempts targeting this vulnerability before a third-party report.
Previdian sensor
Previdian sensors observed exploitation attempts targeting this vulnerability.
GitHub
Public scanner or PoC coverage increases practical exploitability.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| Previdian Sensors First | 2026-10-01 09:44 UTC |
| The Hacker News | 2026-10-01 15:32 UTC |
Operational indicators for this CVE are listed under Detection.
Sensor telemetry
Previdian sensor observations are exploitation attempts targeting this vulnerability. They do not show that the target was vulnerable or that the attempt succeeded. The cards and chart show volume, unique attackers, and daily activity.
53
Attempts observed
20
Unique attacker IPs
15
Attacker countries
AF · BG · CH · CN · FR · HK · ID · JP · LU · NL · SC · SG · UA · US · YE
23
Sensors observed
CVE-2026-1581 exploitation attempts over the last 90 days
Daily events observed by Previdian sensors
Updated 16 Nov 2026
First observed 12 Jun 2026 · Last observed 12 Nov 2026
Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
Nuclei template detected 01 Jun 2026.
View Nuclei template (opens in new tab)Previdian virtual patch guidance is available for this CVE.
Attacker IP indicators observed · available in Pro and Enterprise.
Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.
Learn about Pro API accessScanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-1581.yaml | 01 Jun 2026 |
Compensating WAF rules for this CVE.
Enterprise feature. Virtual patch rule content and deployable vendor exports (ModSecurity, Cloudflare, AWS WAF) are available to Previdian Enterprise users.
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
2.5%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Recent mention · The Hacker News
Cybersecurity researchers have shed light on a WordPress compromise in which threat actors deployed multiple persistence mechanisms to ensure that the final payload kept returning without having to infect the site again. The backdoor has been codenamed SC after the "SC_"...
Read full advisoryRecent mention · The Hacker News
WordPress Backdoor Rebuilds Itself After Cleanup Using Files, Database, and Shared MemoryThe Hacker News · 01 Oct 2026
Cybersecurity researchers have shed light on a WordPress compromise in which threat actors deployed multiple persistence mechanisms to ensure that the final payload kept returning without having to infect the site again. The backdoor has been codenamed SC after the "SC_" markers present in the injected content. Sucuri has described the malware as a "self-healing mesh" that's
These PoCs are unverified and could contain malware. Use at your own risk.
nuclei · Created Unknown
Timeline
11:35 UTC
Compensating WAF rule available to block exploitation
15:32 UTC
Exploitation attempts reported by an external source
13:18 UTC
Indicators of compromise recorded
14:21 UTC
Public proof-of-concept code published
00:34 UTC
Previdian sensors observed exploitation attempts targeting this vulnerability.
15:34 UTC
Scanner coverage available
16:24 UTC
Vulnerability disclosed publicly
00:06 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2026-1581
Sample API response{
"cve_id": "CVE-2026-1581",
"confidence": "Confirmed",
"cvss_score": 7.5,
"cvss_estimated": false,
"epss_score": 0.02507,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": true
},
"sensor_telemetry": { "attempts": 53, "sensors": 23 }
}