CVE-2023-51528

GPT3 AI Content Writer <= 1.8.12 - Cross-Site Request Forgery

2023-12-27 00:00
Brandon James Roldan (tomorrowisnew)

Strategic Overview

Status
Patched in 1.8.13
Affected Plugin
AI Puffer – Chat. Create. Automate. (formerly AI Power)
Affected Version
<= 1.8.12
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-51528
View all AI Puffer – Chat. Create. Automate. (formerly AI Power) vulnerabilities

At a glance

CVE-2023-51528 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the AI Puffer WordPress plugin, affecting versions <= 1.8.12. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.8.13; sites on affected versions should update now. Disclosed December 2023, reported by Brandon James Roldan (tomorrowisnew).

Vulnerability Overview

The GPT3 AI Content Writer plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.12. This is due to missing or incorrect nonce validation on the wpaicg_export_logs_callback() function. This makes it possible for unauthenticated attackers to trigger a log export via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 privileges on the target site.

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

AI Puffer <= 1.8.12 carries this weakness at wpaicg_export_logs_callback(), and reaching it takes a caller who can reach the endpoint. 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 AI Puffer the fix is 1.8.13: builds <= 1.8.12 are affected, anything from 1.8.13 onward is not.

Remediation

Update to version 1.8.13, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to AI Puffer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: AI Puffer 1.8.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-51528https://www.wordfence.com/threat-intel/vulnerabilities/id/5511c5f4-b71c-484b-ab6f-2389a29809cdhttps://nvd.nist.gov/vuln/detail/CVE-2023-51528

Related records

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