CVE-2024-1850

AI Post Generator | AutoWriter <= 3.3 - Missing Authorization

2024-03-21 00:00
Lucio Sá

Strategic Overview

Status
Patched in 3.4
Affected Version
<= 3.3
CVSS
6.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-1850
View all AI Post Generator | AutoWriter vulnerabilities

At a glance

CVE-2024-1850 is a medium-severity Missing Authorization vulnerability in the AI Post Generator WordPress plugin, affecting versions <= 3.3. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.4; sites on affected versions should update now. Disclosed March 2024, reported by Lucio Sá.

Vulnerability Overview

The AI Post Generator | AutoWriter plugin for WordPress is vulnerable to unauthorized access, modification or deletion of posts due to a missing capability check on functions hooked by AJAX actions in all versions up to, and including, 3.3. This makes it possible for authenticated attackers, with subscriber access or higher, to view all posts generated with this plugin (even in non-published status), create new posts (and publish them), publish unpublished post or perform post deletions. CVE-2024-32713 may be a duplicate of this issue.

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.

CWE-862: Missing Authorization

Reaching this weakness in AI Post Generator <= 3.3 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For AI Post Generator the fix is 3.4: builds <= 3.3 are affected, anything from 3.4 onward is not.

Remediation

Update to version 3.4, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: AI Post Generator 3.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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