CVE-2026-7525: Authorization Bypass in My Calendar Plugin
Platform
wordpress
Component
my-calendar
Fixed in
3.7.10
CVE-2026-7525 describes an authorization bypass vulnerability affecting the My Calendar – Accessible Event Manager plugin for WordPress. An authenticated attacker with custom-level access or higher can manipulate the POST body to publish events or alter their status (e.g., cancelled, private) without proper authorization checks. This vulnerability impacts versions 0.0.0 through 3.7.9 and has been resolved in version 3.7.10.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Impact and Attack Scenarios
This vulnerability allows an attacker to bypass the intended moderation and approval workflow within the My Calendar plugin. An attacker with custom-level access can effectively impersonate a higher-privileged user, publishing events that would normally require administrator approval or changing event statuses to reflect cancellations or private settings. This could lead to unauthorized event postings, data manipulation, and potential disruption of scheduled events. The impact is amplified in environments where event scheduling is critical, such as educational institutions, event management platforms, or internal communication systems. Successful exploitation could also be used to inject malicious content into event descriptions or metadata, potentially leading to further attacks.
Exploitation Context
CVE-2026-7525 was published on 2026-05-14. Severity is rated as MEDIUM (CVSS 4.3). No public exploits or active campaigns have been reported at the time of writing. The vulnerability is not currently listed on KEV or EPSS. Monitor security advisories and threat intelligence feeds for any indications of exploitation.
Threat Intelligence
Exploit Status
CISA SSVC
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
- Privileges Required
- Low — any valid user account is sufficient. Basic authenticated access required.
- User Interaction
- None — attack is automatic and silent. Victim does nothing: no click, no file open.
- Scope
- Unchanged — impact is limited to the vulnerable component itself.
- Confidentiality
- None — no confidentiality impact. Attacker cannot read protected data.
- Integrity
- Low — attacker can modify some data with limited scope or impact.
- Availability
- None — no availability impact. Service remains fully operational.
Affected Software
Weakness Classification (CWE)
Timeline
- Reserved
- Published
- Modified
Mitigation and Workarounds
The primary mitigation for CVE-2026-7525 is to immediately upgrade the My Calendar plugin to version 3.7.10 or later. If upgrading is not feasible due to compatibility issues or breaking changes, consider temporarily restricting user roles with custom-level access from modifying event statuses. While not a complete solution, implementing a Web Application Firewall (WAF) with rules to filter suspicious POST requests targeting the plugin's event management endpoints can provide an additional layer of defense. Regularly review user roles and permissions to ensure they align with the principle of least privilege.
How to fix
Update to version 3.7.10, or a newer patched version
Frequently asked questions
What is CVE-2026-7525 — Authorization Bypass in My Calendar plugin?
CVE-2026-7525 is a medium severity authorization bypass vulnerability in the My Calendar plugin for WordPress, allowing attackers with custom-level access to bypass moderation and publish events without proper authorization.
Am I affected by CVE-2026-7525 in My Calendar plugin?
You are affected if your WordPress site uses the My Calendar plugin in versions 0.0.0 through 3.7.9. Upgrade to 3.7.10 or later to resolve the vulnerability.
How do I fix CVE-2026-7525 in My Calendar plugin?
Upgrade the My Calendar plugin to version 3.7.10 or later. If upgrading is not immediately possible, restrict custom-level users' ability to modify event statuses.
Is CVE-2026-7525 being actively exploited?
As of the current assessment, there are no reports of active exploitation or public exploits for CVE-2026-7525, but continuous monitoring is recommended.
Where can I find the official My Calendar advisory for CVE-2026-7525?
Refer to the official My Calendar plugin website and WordPress.org plugin page for updates and security advisories related to CVE-2026-7525.
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Scan your WordPress project now — no account
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...