Vulnerability report

Exploitation attempts observed in the wild High confidence Not in CISA KEV

CVE-2026-28039

wpDataTables

TMS / wpDataTables · 0 to <= 6.5.0.1

Severity
CVSS 7.5 · High
Confidence
High
Exploit status
Exploitation attempts observed in the wild
EPSS
0.4%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-28039 is an unauthenticated vulnerability affecting TMS wpDataTables. Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in TMS wpDataTables...

Have exploitation attempts been observed?

Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Also reported by third-party sources. Confidence is high.

Who is affected?

TMS / wpDataTables 0 to <= 6.5.0.1.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

wpDataTables

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in TMS wpDataTables wpdatatables allows PHP Local File Inclusion.This issue affects wpDataTables: from n/a through 6.5.0.1.

TMS Affected
wpDataTables wpdatatables
Through 6.5.0.1
Published
05 Mar 2026
Exploitation Attempts Reported
27 Oct 2026
Attack vector
Remote
Complexity
High
Privileges
None
User interaction
Required

Tags

wordpress php

CVE References

  • CVE Record CVE.org · CVE Record https://www.cve.org/CVERecord?id=CVE-2026-28039
  • VDB Entry — patchstack.com patchstack.com · VDB Entry https://patchstack.com/database/wordpress/plugin/wpdatatables/vulnera...

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

CVE

Recorded 27 Oct 2026

A trusted third party reported exploitation attempts.

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
CVE First 2026-10-27 07:31 UTC

Detection

Operational artifacts and observed signals

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

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

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

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

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:H/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

0.4%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Timeline

From disclosure to observed exploitation attempts

  1. 07:31 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party report of exploitation attempts

  2. 05:54 UTC

    CVE published

    Vulnerability disclosed publicly

  3. 12:13 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-28039

Sample API response
{
  "cve_id": "CVE-2026-28039",
  "confidence": "High",
  "cvss_score": 7.5,
  "cvss_estimated": false,
  "epss_score": 0.0037,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}