dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-2879

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GetGenie WordPress plugin suffers from an IDOR vulnerability in its REST API endpoint. The create() method accepts a user-controlled post ID without verifying ownership or post type, allowing authenticated Author+ users to overwrite arbitrary posts by changing their post_type to getgenie_chat and reassigning them to the attacker.

MitigationImplement proper authorization checks in the create() method to verify the current user owns the post and that the post is of the expected getgenie_chat type before calling wp_update_post(). Consider role-based access control restrictions on this endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify GetGenie plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'GetGenie' or check wp-content/plugins directory for getgenie folder. Also check wp_options table for getgenie related options.
    Affected if GetGenie plugin is installed and active - the vulnerability only exists in this plugin
  2. Check installed GetGenie version
    Look in the plugin main file header (usually getgenie.php) for the Version: field, or query the WordPress plugins API: GET /wp-json/wp/v2/plugins?search=getgenie
    Affected if Version is within the affected range (compare to known vulnerable versions if available)
  3. Confirm REST API endpoint is accessible
    Test the GetGenie REST API endpoint exists: GET /wp-json/getgenie/v1/chat or similar endpoint path. Check if plugin registers REST routes by inspecting plugin code for register_rest_route() calls.
    Affected if REST API endpoint exists and responds - the vulnerability lives in the create() method of this endpoint
  4. Identify users with Author role or higher
    Query wp_users table joined with wp_usermeta to find users with wp_capabilities meta containing 'author', 'editor', or 'administrator'. Alternatively, check Users > All Users in admin panel.
    Affected if Any user with Author role or higher exists - these roles can exploit the IDOR vulnerability
  5. Check for suspicious getgenie_chat post type changes
    Query wp_posts table: SELECT * FROM wp_posts WHERE post_type='getgenie_chat' AND post_author NOT IN (SELECT ID FROM wp_users WHERE user_status=0). Also look for posts where post_type was changed from other types to getgenie_chat.
    Affected if Posts exist where post_type='getgenie_chat' but the author differs from expected, or posts were reassigned to different authors

The environment is affected if GetGenie plugin is installed with a vulnerable version, its REST API is active, and there are Author+ users present who could exploit the IDOR by manipulating post IDs and post_type to getgenie_chat.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks in the create() method to verify the current user owns the post and that the post is of the expected getgenie_chat type before calling wp_update_post(). Consider role-based access control restrictions on this endpoint.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2879 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2879 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data