# CVE-2026-4124: Missing authorization in Ziggeo

> Authenticated subscribers can modify arbitrary plugin settings and data due to missing capability checks in the Ziggeo WordPress plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-8w6x-cfx6-w753

## What is CVE-2026-4124?

CVE-2026-4124 is a medium-severity missing authorization vulnerability in oliverfriedmann Ziggeo, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Ziggeo plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.1.1. The wp_ajax_ziggeo_ajax handler  only verifies a nonce (check_ajax_referer) but performs no capability checks via current_user_can(). Furthermore, the nonce ('ziggeo_ajax_nonce') is exposed to all logged-in users on every page via the wp_head and admin_head hooks . This makes it possible for authenticated attackers, with Subscriber-level access and above, to invoke multiple administrative operations including: saving arbitrary translation strings (translations_panel_save_strings via update_option('ziggeo_translations')), creating/updating/deleting event templates (event_editor_save_template/update_template/remove_template via update_option('ziggeo_events')), modifying SDK application settings (sdk_applications operations), and managing notifications (notification_handler via update_option('ziggeo_notifications')).

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-4124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4124 is a medium-severity missing authorization vulnerability in oliverfriedmann Ziggeo, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4124 in the wild and no public exploit code.

Affected product: oliverfriedmann Ziggeo. 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-4124/ (Markdown: https://insights.sbomify.com/CVE-2026-4124/index.md)
```

## Sources

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

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