GetGenie <= 4.3.2 - Insecure Direct Object Reference to Authenticated (Author+) Arbitrary Post Overwrite/Deletion
Strategic Overview
- Status
- Patched in 4.3.3
- Affected Version
<= 4.3.2- CVSS
- 5.4Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-2879
At a glance
CVE-2026-2879 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the GetGenie WordPress plugin, affecting versions <= 4.3.2. It carries a CVSS score of 5.4 (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.3; sites on affected versions should update now. Disclosed March 2026, reported by Kazuma Matsumoto.
Vulnerability Overview
The GetGenie plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.2. This is due to missing validation on the `id` parameter in the `create()` method of the `GetGenieChat` REST API endpoint. The method accepts a user-controlled post ID and, when a post with that ID exists, calls `wp_update_post()` without verifying that the current user owns the post or that the post is of the expected `getgenie_chat` type. This makes it possible for authenticated attackers, with Author-level access and above, to overwrite arbitrary posts owned by any user — including Administrators — effectively destroying the original content by changing its `post_type` to `getgenie_chat` and reassigning `post_author` to the attacker.
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-639: Authorization Bypass Through User-Controlled Key
GetGenie <= 4.3.2 carries this weakness at create(), and reaching it takes an account at Author level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For GetGenie the fix is 4.3.3: builds <= 4.3.2 are affected, anything from 4.3.3 onward is not.
Remediation
Update to version 4.3.3, 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.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO
- 7.2CVE-2026-65440: GetGenie <= 4.4.3 Stored Cross-Site Scripting
CVE-2026-65440 - 5.3CVE-2026-54197: GetGenie Information Exposure
CVE-2026-54197 - 4.3CVE-2026-57316: GetGenie Info Exposure
CVE-2026-57316 - 4.3CVE-2026-1003: GetGenie Authenticated (Author+) Arbitrary Post
CVE-2026-1003 - 4.3CVE-2026-24356: GetGenie <= 4.3.0 Missing Authorization
CVE-2026-24356
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C