Vulnerability report

Exploitation Attempts Observed Confirmed Confidence Not in CISA KEV

CVE-2026-1581

wpForo Forum <= 2.4.14 - Unauthenticated Time-Based SQL Injection

Tomdever / wpForo Forum · * to <= 2.4.14

Severity
CVSS 7.5 · High
Confidence
Confirmed
Exploit status
Exploitation Attempts Observed in the Wild
EPSS
2.5%
First observed
12 Jun 2026
Last observed
12 Nov 2026

Decision summary

What security teams need to know first

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

wpForo Forum <= 2.4.14 - Unauthenticated Time-Based SQL Injection

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.

tomdever Affected
wpForo Forum
Through 2.4.14
Published
19 Feb 2026
Exploitation Attempts Reported
12 Jun 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

wordpress nuclei_scanner

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation Attempts Observed in the Wild

Previdian

Recorded 12 Jun 2026

Previdian sensors observed exploitation attempts targeting this vulnerability before a third-party report.

Exploitation Attempts Observed

Previdian sensor

First observed 12 Jun 2026

Previdian sensors observed exploitation attempts targeting this vulnerability.

Proof of concept available

GitHub

Recorded 27 Feb 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

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

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

0
1
0
1
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
1
1
0
0
2
0
0
2
1
1
0
4
7
2
2
0
5
5
3
1
1
0
0
0
0
0
1
0
2
2
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
1
1
0
0
1
0
0
0
0
19 Aug 6 Sep 24 Sep 12 Oct 16 Nov

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.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
1
10
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

Previdian virtual patch guidance is available for this CVE.

AWS WAF Cloudflare ModSecurity

Attacker IP Indicators

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 access

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Virtual Patch Detail

Compensating WAF rules for this CVE.

Available

Enterprise feature. Virtual patch rule content and deployable vendor exports (ModSecurity, Cloudflare, AWS WAF) are available to Previdian Enterprise users.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

7.5 High

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

WordPress Backdoor Rebuilds Itself After Cleanup Using Files, Database, and Shared Memory

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 advisory

All Mentions

Recent mention · The Hacker News

WordPress Backdoor Rebuilds Itself After Cleanup Using Files, Database, and Shared Memory

The 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

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Timeline

From disclosure to observed exploitation attempts

  1. 11:35 UTC

    Virtual patch available

    Compensating WAF rule available to block exploitation

  2. 15:32 UTC

    KEV confirmed by The Hacker News

    Exploitation attempts reported by an external source

  3. 13:18 UTC

    Indicators of compromise added (16)

    Indicators of compromise recorded

  4. 14:21 UTC

    Public PoC available

    Public proof-of-concept code published

  5. 00:34 UTC

    Observed by Previdian sensors

    Previdian sensors observed exploitation attempts targeting this vulnerability.

  6. 15:34 UTC

    Nuclei template available

    Scanner coverage available

  7. 16:24 UTC

    CVE published

    Vulnerability disclosed publicly

  8. 00:06 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

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 }
}