Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

WP jQuery DataTable Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with WP jQuery DataTable, published between 2025 and 2025.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

3Total records
0Critical
0High
3Medium
0Low
0Informational
2Patched records
1Currently marked unpatched
2025-01-03First disclosure
2025-05-07Latest disclosure
3 of 3CVE coverage

Use this history

Check and watch WP jQuery DataTable.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
202533 records

Severity Breakdown

SeverityRecordsShare
Medium3100%

Vulnerability-Type Breakdown

Cross-Site Scripting

3 records100%

First: 2025. Latest: 2025.

Patch Status

Patched
2
Currently marked unpatched
1
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 4.1.0

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-4.1.0WP jQuery DataTable <= 4.1.0 - Authenticated (Administrator+) Stored Cross-Site ScriptingMay 7, 2025Not suppliedMedium
*-4.0.1WP jQuery DataTable <= 4.0.1 - Authenticated (Contributor+) Stored Cross-Site ScriptingJanuary 6, 20254.1.0Medium
*-4.0.1WP jQuery DataTable <= 4.0.1 - Authenticated (Contributor+) Stored Cross-Site ScriptingJanuary 3, 20254.1.0Medium

Selected source records

Latest Records

MediumCVE-2025-47605

WP jQuery DataTable <= 4.1.0 - Authenticated (Administrator+) Stored Cross-Site Scripting

Published: May 7, 2025

Affected versions
*-4.1.0
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-12499

WP jQuery DataTable <= 4.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: January 6, 2025

Affected versions
*-4.0.1
Patched versions
4.1.0
Original Wordfence record
MediumCVE-2024-56287

WP jQuery DataTable <= 4.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: January 3, 2025

Affected versions
*-4.0.1
Patched versions
4.1.0
Original Wordfence record

Highest-Severity Records

MediumCVE-2024-56287

WP jQuery DataTable <= 4.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: January 3, 2025

Affected versions
*-4.0.1
Patched versions
4.1.0
Original Wordfence record
MediumCVE-2024-12499

WP jQuery DataTable <= 4.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: January 6, 2025

Affected versions
*-4.0.1
Patched versions
4.1.0
Original Wordfence record
MediumCVE-2025-47605

WP jQuery DataTable <= 4.1.0 - Authenticated (Administrator+) Stored Cross-Site Scripting

Published: May 7, 2025

Affected versions
*-4.1.0
Patched versions
Not supplied
Original Wordfence record

Currently Marked Unpatched Records

MediumCVE-2025-47605

WP jQuery DataTable <= 4.1.0 - Authenticated (Administrator+) Stored Cross-Site Scripting

Published: May 7, 2025

Affected versions
*-4.1.0
Patched versions
Not supplied
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory