LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2879: GetGenie <= 4.3.2 - Insecure Direct Object Reference to Authenticated (Author+) Arbitrary Post Overwrite/Deletion

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-2879 affects the GetGenie WordPress plugin through version 4.3.2. A logged-in user with Author-level access or higher could overwrite posts belonging to others, including administrators. The main business risk is content integrity loss and disruption, not server takeover.

Executive priority

Treat as a moderate-priority content integrity issue. Prioritize sites with many contributors, external authors, or business-critical published content. This is not described as remote unauthenticated compromise, but it can damage or erase visible content workflows.

Technical view

The GetGenieChat REST API create() method lacks ownership and post-type validation for a user-controlled id parameter. If the referenced post exists, it can call wp_update_post(), changing the post type to getgenie_chat and reassigning authorship to the attacker. This is CWE-639 insecure direct object reference.

Likely exposure

Exposure is limited to WordPress sites running GetGenie up to and including 4.3.2 where attackers can authenticate as Author or higher. Sites without untrusted Author-level users have lower practical exposure.

Exploitation context

The CVSS vector is network-accessible, low complexity, low privilege, and no user interaction. The source bundle does not indicate CISA KEV listing or active exploitation. Impact is integrity and availability of WordPress content.

Researcher notes

Evidence points to missing object-level authorization in a REST endpoint. The affected-version statement is clear in the description, but the provided affected metadata is inconsistent and no fixed version is explicitly named in the bundle.

Mitigation direction

  • Check vendor and WordPress plugin guidance for the fixed version or official remediation.
  • Update GetGenie if a fixed release is available from trusted channels.
  • Restrict Author-level and higher accounts to trusted users only.
  • Temporarily disable GetGenie if content integrity risk is unacceptable.
  • Ensure recent WordPress database and content backups are available.

Validation and detection

  • Inventory WordPress sites for GetGenie installations and versions.
  • Flag sites running GetGenie 4.3.2 or earlier.
  • Review Author-level and higher accounts for unnecessary access.
  • Check content history for unexpected author or post_type changes.
  • Confirm remediation by verifying plugin version after update.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2879 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-2879Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
roxnorGetGenie – AI Content Writer with Keyword Research & SEO Tracking Tools0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.