LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25008: WordPress Ninja Tables plugin <= 5.2.5 - Sensitive Data Exposure vulnerability

Insertion of Sensitive Information Into Sent Data vulnerability in Shahjahan Jewel Ninja Tables ninja-tables allows Retrieve Embedded Sensitive Data.This issue affects Ninja Tables: from n/a through <= 5.2.5.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25008 is a medium-severity sensitive data exposure issue in the WordPress Ninja Tables plugin through version 5.2.5. An authenticated user could retrieve embedded sensitive data sent by the plugin. Business urgency is moderate: prioritize sites where Ninja Tables handles private, customer, or internal table data.

Executive priority

Schedule remediation in the normal vulnerability cycle, faster for sites containing regulated, customer, or confidential data. This is not currently evidenced as actively exploited, but it can expose sensitive information to authenticated users.

Technical view

The issue is classified as CWE-201: insertion of sensitive information into sent data. CVSS 3.1 is 4.3: network exploitable, low complexity, low privileges required, no user interaction, low confidentiality impact, and no integrity or availability impact. Sources identify Ninja Tables <= 5.2.5 as affected, but do not name a fixed version.

Likely exposure

Exposure is limited to WordPress sites running Ninja Tables through 5.2.5, especially where authenticated users have access to table views or plugin functionality. Risk depends on what sensitive information is embedded in data returned by the plugin.

Exploitation context

The CVSS vector indicates exploitation requires low-privileged authenticated access over the network. The source bundle does not indicate public exploit code, active exploitation, or CISA KEV listing. Treat exploitation status as unconfirmed, not actively exploited.

Researcher notes

Evidence is limited to the CVE record and Patchstack reference. The bundle lists affected versions through 5.2.5 but does not provide a fixed version or detailed reproduction conditions. Avoid assuming unauthenticated exposure; CVSS states privileges are required.

Mitigation direction

  • Inventory WordPress sites using the Ninja Tables plugin.
  • Identify installations running Ninja Tables version 5.2.5 or earlier.
  • Check vendor or plugin repository guidance for a fixed release.
  • Update the plugin if a vendor-supported fixed version is available.
  • Restrict plugin access to trusted authenticated users until remediated.
  • Review tables for embedded secrets, tokens, or private data.

Validation and detection

  • Confirm the installed Ninja Tables version in WordPress admin or asset inventory.
  • Verify whether affected sites expose sensitive table data to authenticated users.
  • Review plugin changelog or vendor advisory for the fixed version.
  • After updating, retest access paths for unintended sensitive data exposure.
  • Check logs for unusual authenticated access to Ninja Tables content.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25008 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-25008Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Shahjahan JewelNinja Tablesninja-tables, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.