HomeWordPress vulnerabilitiesGetGenie
GetGenie vulnerabilities
GetGenie has 3 known vulnerabilities in this database. The most recent published record is dated 13 Mar 2026.
- Known vulnerabilities
- 3
- Active installs
- 80,000+
- Latest version
- 4.5.6
- Last updated
- 7 Sep 2026
- Most recent
- 13 Mar 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-2879 | Medium 5.4 | Up to 4.3.2 | Fixed in a later version (latest 4.5.6) | 13 Mar 2026 |
| Cross-site scripting (XSS) CVE-2026-2257 | Medium 6.4 | Up to 4.3.2 | Fixed in a later version (latest 4.5.6) | 13 Mar 2026 |
| Broken access control CVE-2026-1003 | Medium 4.3 | Up to 4.3.0 | Fixed in a later version (latest 4.5.6) | 16 Jan 2026 |
Read the published descriptions
- CVE-2026-2879, 13 Mar 2026
- 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. CVE record
- CVE-2026-2257, 13 Mar 2026
- The GetGenie plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.3.2 due to missing validation on a user controlled key in the `action` function. This makes it possible for authenticated attackers, with Author-level access and above, to update post metadata for arbitrary posts. Combined with a lack of input sanitization, this leads to Stored Cross-Site Scripting when a higher-privileged user (such as an Administrator) views the affected post's "Competitor" tab in the GetGenie sidebar. CVE record
- CVE-2026-1003, 16 Jan 2026
- The GetGenie plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.3.0. This is due to the plugin not properly verifying that a user is authorized to delete a specific post. This makes it possible for authenticated attackers, with Author-level access and above, to delete any post on the WordPress site, including posts authored by other users. CVE record
What to do if you run GetGenie
If you run GetGenie, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new GetGenie vulnerabilities
Free. We email you when a new vulnerability is published for GetGenie, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.