CVE-2026-1003

GetGenie – AI Content Writer with Keyword Research & SEO Tracking Tools <= 4.3.0 - Missing Authorization to Authenticated (Author+) Arbitrary Post Deletion

2026-01-15 00:00
theviper17y

Strategic Overview

Status
Patched in 4.3.1
Affected Version
<= 4.3.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1003
View all GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO vulnerabilities

At a glance

CVE-2026-1003 is a medium-severity Missing Authorization vulnerability in the GetGenie WordPress plugin, affecting versions <= 4.3.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. The issue is fixed in version 4.3.1; sites on affected versions should update now. Disclosed January 2026, reported by theviper17y.

Vulnerability Overview

The GetGenie plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.3.0. This is due to the plugin not properly verifying that a user is authorized to delete a specific post. This makes it possible for authenticated attackers, with Author-level access and above, to delete any post on the WordPress site, including posts authored by other users.

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 GetGenie <= 4.3.0 takes an account at Author level or above. 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 GetGenie the fix is 4.3.1: builds <= 4.3.0 are affected, anything from 4.3.1 onward is not.

Remediation

Update to version 4.3.1, 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: GetGenie 4.3.1 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