CVE-2023-6967

Pods - Custom Content Types and Fields - Authenticated (Contributor+) SQL Injection via Shortcode

2024-03-28 00:00
Nex Team

Strategic Overview

Status
Patched in 2.7.31.2
Affected Plugin
Pods – Custom Content Types and Fields
Affected Version
2.7.31 – < 3.0.10.2 · 3 branches
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2023-6967
View all Pods – Custom Content Types and Fields vulnerabilities

At a glance

CVE-2023-6967 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Pods WordPress plugin, affecting versions 2.7.31 – < 3.0.10.2 · 3 branches. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.7.31.2; sites on affected versions should update now. Disclosed March 2024, reported by Nex Team.

Vulnerability Overview

The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to SQL Injection via shortcode in all versions up to, and including, 3.0.10 (with the exception of 2.7.31.2, 2.8.23.2, 2.9.19.2) due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor level access or higher, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Pods 2.7.31 – < 3.0.10.2 · 3 branches takes an account at Contributor level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Pods the fix is 2.7.31.2: builds 2.7.31 – < 3.0.10.2 · 3 branches are affected, anything from 2.7.31.2 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 2.7.31.2, 2.8.23.2, 2.9.19.2, 3.0.10.2

How does WordSec protect against this?

An attacker needs Contributor 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: Pods 2.7.31.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6967https://www.wordfence.com/threat-intel/vulnerabilities/id/1aa7d0c2-27ec-47ad-8baa-c281c273078ehttps://nvd.nist.gov/vuln/detail/CVE-2023-6967

Related records

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