Radar sectionsDatabase
Check my site
WordPress plugin

GetGenie <= 4.3.2 — Insecure Direct Object Reference to Authenticated (Author+) Arbitrary Post Overwrite/Deletion

CVE-2026-2879Published · Updated

Action summary

Affected: ≤4.3.2Update to 4.3.3 or newer

All remediation steps
Severity
Medium5.4
CVSS
5.4
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:L Availability
Low
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO getgenie

  1. Affected≤ 4.3.2
  2. Patched in4.3.3

Update to 4.3.3 or newer.

You are affected if you run ≤ 4.3.2. Version 4.3.3 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 4.3.3, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Kazuma Matsumoto.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO

All 7
More vulnerabilities in GetGenie – AI SEO Assistant & Content Writer with Keyword Research, AEO & GEO
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting
≤4.4.3Update to 4.5.0
CVE-2026-65440
Medium4.3Authenticated (Subscriber+) Sensitive Information Exposure
≤4.4.2Update to 4.4.3
CVE-2026-57316
Medium5.3Unauthenticated Information Exposure
≤4.4.1Update to 4.4.2
CVE-2026-54197
Medium6.4Insecure Direct Object Reference to Authenticated (Author+) Stored Cross-Site Scripting via REST API
≤4.3.2Update to 4.3.3
CVE-2026-2257
Medium4.3Missing Authorization to Authenticated (Author+) Arbitrary Post Deletion
≤4.3.0Update to 4.3.1
CVE-2026-1003

Timeline

  1. CVE published

    Severity medium, CVSS 5.4

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?