CVE-2026-4124 json
Ziggeo <= 3.1.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Modification via 'ziggeo_ajax' AJAX Action
published 7mo ago modified 3mo ago also EUVD-2026-20842
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
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')).
Is CVE-2026-4124 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
Affected products
- oliverfriedmann Ziggeo
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/15477c00-0764-4850-8bce-d65b6b1cbe4c?source=cve
- plugins.trac.wordpress.org /browser/ziggeo/trunk/core/ajax.php#L31
- plugins.trac.wordpress.org /browser/ziggeo/tags/3.1.1/core/ajax.php#L31
- plugins.trac.wordpress.org /browser/ziggeo/trunk/admin/page_translations_ajax.php#L13
- plugins.trac.wordpress.org /browser/ziggeo/tags/3.1.1/admin/page_translations_ajax.php#L13
- plugins.trac.wordpress.org /browser/ziggeo/trunk/admin/page_editor_events_ajax.php#L13
- plugins.trac.wordpress.org /browser/ziggeo/tags/3.1.1/admin/page_editor_events_ajax.php#L13
- plugins.trac.wordpress.org /browser/ziggeo/trunk/admin/page_sdk_ajax.php#L8
- plugins.trac.wordpress.org /browser/ziggeo/tags/3.1.1/admin/page_sdk_ajax.php#L8
- plugins.trac.wordpress.org /browser/ziggeo/trunk/core/header.php#L67
- plugins.trac.wordpress.org /browser/ziggeo/tags/3.1.1/core/header.php#L67
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3494290%40ziggeo&new=3494290%40ziggeo&sfp_email=&sfph_mail=
Sources
- CVE List CVE-2026-4124
- NVD CVE-2026-4124
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.