CVE-2026-2879
Received Received - Intake
Insecure Direct Object Reference in GetGenie WordPress Plugin Allows Post Overwrite

Publication date: 2026-03-13

Last updated on: 2026-03-13

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-13
Last Modified
2026-03-13
Generated
2026-05-27
AI Q&A
2026-03-13
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
getgenie getgenie_plugin to 4.3.2 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The GetGenie plugin for WordPress has a vulnerability called Insecure Direct Object Reference (IDOR) in all versions up to and including 4.3.2. This happens because the plugin does not properly validate the 'id' parameter in the 'create()' method of the GetGenieChat REST API endpoint.

An attacker with Author-level access or higher can supply a post ID they control. The method then calls 'wp_update_post()' without checking if the user owns the post or if the post is of the expected type. This allows the attacker to overwrite posts owned by any user, including administrators, by changing the post type and reassigning ownership.


How can this vulnerability impact me? :

This vulnerability allows an authenticated attacker with Author-level access or above to overwrite arbitrary posts owned by any user, including administrators.

The attacker can effectively destroy the original content by changing the post type to 'getgenie_chat' and reassigning the post author to themselves, potentially leading to data loss, content tampering, and unauthorized content control.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart