此页面尚未翻译为您的语言。我们正在努力翻译,目前显示英文内容。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-7525: Authorization Bypass in My Calendar Plugin
平台
wordpress
组件
my-calendar
修复版本
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.
检测此 CVE 是否影响你的项目
上传你的依赖文件,立即了解此CVE和其他CVE是否影响你。
影响与攻击场景翻译中…
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.
利用背景翻译中…
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.
威胁情报
漏洞利用状态
CISA SSVC
CVSS 向量
这些指标意味着什么?
- Attack Vector
- 网络 — 可通过互联网远程利用,无需物理或本地访问。攻击面最大。
- Attack Complexity
- 低 — 无需特殊条件,可以稳定地利用漏洞。
- Privileges Required
- 低 — 任何有效用户账户均可。
- User Interaction
- 无 — 攻击自动且无声,受害者无需任何操作。
- Scope
- 未改变 — 影响仅限于脆弱组件本身。
- Confidentiality
- 无 — 无机密性影响。
- Integrity
- 低 — 攻击者可修改部分数据,影响有限。
- Availability
- 无 — 无可用性影响。
受影响的软件
弱点分类 (CWE)
时间线
- 已保留
- 发布日期
- 修改日期
缓解措施和替代方案翻译中…
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.
修复方法
更新至 3.7.10 版本,或更新的补丁版本
常见问题翻译中…
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.
检测此 CVE 是否影响你的项目
上传你的依赖文件,立即了解此CVE和其他CVE是否影响你。
立即扫描您的WordPress项目 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始:拥有账户后,您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...