MEDIUMCVE-2025-32218CVSS 4.3

CVE-2025-32218: Unauthorized Access in TableOn WordPress Plugin

Platform

wordpress

Component

posts-table-filterable

Fixed in

1.0.6

CVE-2025-32218 affects the TableOn – WordPress Posts Table Filterable plugin, a popular WordPress extension. This vulnerability allows authenticated attackers, specifically those with Subscriber-level access or higher, to execute unauthorized actions within the plugin. The issue stems from a missing capability check, enabling privilege escalation. Affected versions include those prior to 1.0.6, with a fix released in version 1.0.6.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

Impact and Attack Scenarios

The primary impact of CVE-2025-32218 is unauthorized access and potential data manipulation. An attacker with Subscriber privileges could leverage this vulnerability to modify table configurations, potentially exposing sensitive data or altering the plugin's functionality. While the attacker requires authentication, the ease of obtaining Subscriber access on many WordPress sites significantly broadens the attack surface. This could lead to defacement, data breaches, or even the injection of malicious code through the plugin's interface. The blast radius is limited to the scope of the plugin's functionality and the data it manages, but the potential for disruption and data compromise remains significant.

Exploitation Context

CVE-2025-32218 is currently not listed on KEV or EPSS, indicating a low to medium probability of active exploitation. Public proof-of-concept (POC) code has not been widely reported. The vulnerability was published on 2025-04-04, and it’s possible that threat actors are actively analyzing it. Monitor WordPress security forums and vulnerability databases for any signs of exploitation.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh

EPSS

0.34% (56% percentile)

CISA SSVC

Exploitationnone
Automatableno
Technical Impactpartial

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N4.3MEDIUMAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredLowAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeUnchangedImpact beyond the vulnerable componentConfidentialityNoneRisk of sensitive data exposureIntegrityLowRisk of unauthorized data modificationAvailabilityNoneRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
Low — any valid user account is sufficient. Basic authenticated access required.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Unchanged — impact is limited to the vulnerable component itself.
Confidentiality
None — no confidentiality impact. Attacker cannot read protected data.
Integrity
Low — attacker can modify some data with limited scope or impact.
Availability
None — no availability impact. Service remains fully operational.

Affected Software

Componentposts-table-filterable
Vendorwordfence
Maximum version1.0.5.1
Fixed in1.0.6

Weakness Classification (CWE)

Timeline

  1. Reserved
  2. Published
  3. Modified
  4. EPSS updated

Mitigation and Workarounds

The primary mitigation for CVE-2025-32218 is to immediately upgrade the TableOn – WordPress Posts Table Filterable plugin to version 1.0.6 or later. If upgrading is not immediately feasible due to compatibility issues or testing requirements, consider temporarily restricting access to the plugin's administrative interface to users with higher privileges. While a WAF or proxy rule cannot directly address the missing capability check, implementing strict access controls and monitoring plugin activity can help detect and prevent exploitation attempts. Regularly review user roles and permissions within WordPress to ensure the principle of least privilege is enforced.

How to fix

Update to version 1.0.6, or a newer patched version

Frequently asked questions

What is CVE-2025-32218 — Unauthorized Access in TableOn WordPress Plugin?

CVE-2025-32218 is a medium severity vulnerability affecting the TableOn WordPress plugin. It allows authenticated attackers with Subscriber access to perform unauthorized actions due to a missing capability check, potentially leading to data manipulation or plugin compromise.

Am I affected by CVE-2025-32218 in TableOn WordPress Plugin?

You are affected if you are using TableOn WordPress Posts Table Filterable plugin versions equal to or less than 1.0.5.1. Check your plugin version and upgrade immediately if vulnerable.

How do I fix CVE-2025-32218 in TableOn WordPress Plugin?

Upgrade the TableOn WordPress Posts Table Filterable plugin to version 1.0.6 or later. If upgrading is not immediately possible, restrict access to the plugin's administrative interface to users with higher privileges.

Is CVE-2025-32218 being actively exploited?

Currently, there are no widespread reports of active exploitation. However, it's possible that threat actors are analyzing the vulnerability, so vigilance is advised.

Where can I find the official TableOn advisory for CVE-2025-32218?

Refer to the TableOn plugin's official website or WordPress plugin repository for the latest advisory and update information regarding CVE-2025-32218.

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

WordPress

Detect this CVE in your project

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

livefree scan

Scan your WordPress project now — no account

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...