# CVE-2026-120578: The AI Alt Text Generator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.7.0.


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-5r5r-rf5q-8h3p

## What is CVE-2026-120578?

CVE-2026-120578 is a medium-severity vulnerability in migkapa AI Alt Text Generator, published on 3 Nov 2026. 

### Official description

The AI Alt Text Generator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.7.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to modify the alt text, and optionally the title, caption, and description of arbitrary attachments owned by other users. Exploiting this vulnerability requires a Contributor-level account to retrieve the nonce from the page source of post.php, post-new.php, or upload.php; additionally, overwriting post_title, post_excerpt, and post_content requires the plugin's set_title, set_caption, or set_description options to be enabled.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-120578?


## How do I fix CVE-2026-120578?

No fix has been published for CVE-2026-120578 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120578 being exploited?

There is no known exploitation of CVE-2026-120578 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120578 and fix it if it is affected.

What it is: CVE-2026-120578 is a medium-severity vulnerability in migkapa AI Alt Text Generator, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120578 in the wild and no public exploit code.

Affected product: migkapa AI Alt Text Generator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120578/ (Markdown: https://insights.sbomify.com/CVE-2026-120578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120578
- OSV: https://osv.dev/vulnerability/CVE-2026-120578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120578/
Summaries are generated and may contain mistakes; the official description above is the record.
