CVE-2026-7525 json
My Calendar <= 3.7.9 - Authenticated (Custom+) Missing Authorization to Unauthorized Event Publication via 'event_approved' Parameter
published 5mo ago modified 4mo ago also EUVD-2026-30217
- cvss
- 4.3
- 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 27%
- public exploits
- 0
- none known
Summary
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.7.9. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with custom-level access and above, to bypass the moderation and approval workflow by tampering with the POST body to publish events or set other unauthorized statuses such as cancelled or private, in ways their role does not permit. While the UI correctly restricts low-privilege users to a draft-only submit button, this restriction is enforced only client-side, making it trivially bypassable by directly manipulating the POST request.
Patch / fix
Is CVE-2026-7525 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
- 5mo ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- joedolson My Calendar – Accessible Event Manager
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- github.com /joedolson/my-calendar/commit/98aef8fbfc6ca4cfe50aaa36761d5f1eb629dfe4
- wordfence.com /threat-intel/vulnerabilities/id/3e27c0b0-c74f-47ad-b9ed-9fd6bd05d040?source=cve
- plugins.trac.wordpress.org /browser/my-calendar/trunk/my-calendar-event-editor.php#L2384
- plugins.trac.wordpress.org /browser/my-calendar/tags/3.7.9/my-calendar-event-editor.php#L2384
- plugins.trac.wordpress.org /browser/my-calendar/trunk/my-calendar-event-editor.php#L406
- plugins.trac.wordpress.org /browser/my-calendar/tags/3.7.9/my-calendar-event-editor.php#L406
- plugins.trac.wordpress.org /browser/my-calendar/trunk/my-calendar-event-editor.php#L601
- plugins.trac.wordpress.org /browser/my-calendar/tags/3.7.9/my-calendar-event-editor.php#L601
- plugins.trac.wordpress.org /browser/my-calendar/tags/3.7.4/my-calendar-event-editor.php#L2384
- plugins.trac.wordpress.org /browser/my-calendar/tags/3.7.4/my-calendar-event-editor.php#L406
- plugins.trac.wordpress.org /browser/my-calendar/tags/3.7.4/my-calendar-event-editor.php#L601
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3527861%40my-calendar&new=3527861%40my-calendar&sfp_email=&sfph
Sources
- CVE List CVE-2026-7525
- NVD CVE-2026-7525
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.