Vulnerability report

Active exploitation 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
Observed in sensors
EPSS
1.7%
First observed
12 Jun 2026
Last observed
30 Sep 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. The wpForo Forum plugin for WordPress is vulnerable to time-based SQL Injection via the 'wpfob' parameter in all...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence. Also confirmed by third-party sources.

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 Reported
12 Jun 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

wordpress

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

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

Exploited in the wild

Previdian

Recorded 12 Jun 2026

Previdian independently recorded this as exploited after first seeing it in honeypot sensors.

Active exploitation observed

Previdian sensor

First observed 12 Jun 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

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

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

7

Attempts observed

5

Unique attacker IPs

5

Attacker countries

BG · CH · FR · US · YE

6

Sensors observed

CVE-2026-1581 exploitation attempts over the last 91 days

Daily events observed by Previdian sensors

Updated 01 Oct 2026

9
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
1
0
0
0
0
1
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
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
0
3 Jul 22 Jul 10 Aug 29 Aug 1 Oct

First observed 12 Jun 2026 · Last observed 30 Sep 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Request telemetry access

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

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

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

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.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

1.7%

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

Potential Proof of Concepts

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

Timeline

From disclosure to observed exploitation

  1. 15:32 UTC

    KEV confirmed by The Hacker News

    Exploitation attested by an external source

  2. 13:18 UTC

    Indicators of compromise added (5)

    Indicators of compromise recorded

  3. 14:21 UTC

    Public PoC available

    Public proof-of-concept code published

  4. 00:34 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  5. 15:34 UTC

    Nuclei template available

    Scanner coverage available

  6. 16:24 UTC

    CVE published

    Vulnerability disclosed publicly

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

Free JSON includes basic KEV fields
{
  "cve_id": "CVE-2026-1581",
  "confidence": "Confirmed",
  "cvss_score": 7.5,
  "cvss_estimated": false,
  "epss_score": 0.01727,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 7, "sensors": 6 }
}