CVE-2022-46852

WP Table Builder – WordPress Table Plugin <= 1.4.6 - Authenticated (Admin+) Stored Cross-Site Scripting

2023-02-20 00:00
Muhammad Daffa

Strategic Overview

Status
Patched in 1.4.7
Affected Version
<= 1.4.6
CVSS
4.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-46852
View all WP Table Builder – Drag & Drop Table Builder vulnerabilities

At a glance

CVE-2022-46852 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Table Builder WordPress plugin, affecting versions <= 1.4.6. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.4.7; sites on affected versions should update now. Disclosed February 2023, reported by Muhammad Daffa.

Vulnerability Overview

The WP Table Builder – WordPress Table Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via an unknown parameter in versions up to, and including, 1.4.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level privileges, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Table Builder <= 1.4.6 takes an account at Admin level or above. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Table Builder the fix is 1.4.7: builds <= 1.4.6 are affected, anything from 1.4.7 onward is not.

Remediation

Update to version 1.4.7, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Table Builder 1.4.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C