Genolve – AI image AI video generation <= 5.0.5 - Authenticated (Contributor+) Incorrect Authorization to Privilege Escalation via theopt
Strategic Overview
- Status
- Patched in 5.0.6
- Affected Plugin
- Genolve – Genolve AI Business Graphics, AI Images
- Affected Version
<= 5.0.5- CVSS
- 8.8High
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2026-1359
At a glance
CVE-2026-1359 is a high-severity Incorrect Authorization vulnerability in the Genolve WordPress plugin, affecting versions <= 5.0.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 5.0.6; sites on affected versions should update now. Disclosed July 2026, reported by Kazuma Matsumoto.
Vulnerability Overview
The Genolve – AI image AI video generation plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the genolve_setOpt() function in all versions up to, and including, 5.0.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to update arbitrary WordPress options, including enabling user registration and setting the default role to administrator, resulting in privilege escalation.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-863: Incorrect Authorization
Genolve <= 5.0.5 carries this weakness at genolve_setOpt(), and reaching it takes an account at Contributor level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Genolve the fix is 5.0.6: builds <= 5.0.5 are affected, anything from 5.0.6 onward is not.
Remediation
Update to version 5.0.6, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Genolve 5.0.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C