dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-68979

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authorization Bypass Through User-Controlled Key vulnerability in SimpleCalendar Google Calendar Events google-calendar-events allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Google Calendar Events: from n/a through <= 3.5.9.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an authorization bypass vulnerability in the SimpleCalendar Google Calendar Events WordPress plugin where an attacker can control a key used for authorization decisions, allowing them to bypass access controls. The vulnerability stems from incorrectly configured access control security levels that rely on user-supplied input without proper validation.

MitigationUpdate the SimpleCalendar Google Calendar Events plugin to the latest version which should contain a fix for this authorization bypass. If no update is available, implement additional server-side validation of authorization keys and review access control logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SimpleCalendar plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'SimpleCalendar Google Calendar Events' in the installed plugins list
    Affected if Plugin is installed and active
  2. Identify installed plugin version
    In Plugins list, click on the plugin name to view details, or check the plugin header file via file manager at /wp-content/plugins/simple-calendar/
    Affected if Version cannot be determined or is earlier than the patched release
  3. Verify Google Calendar feed is configured
    Go to SimpleCalendar > Calendars and check if any calendar feed is configured to use Google Calendar as the source
    Affected if Google Calendar feed integration is active and configured
  4. Inspect authorization key configuration
    Check the plugin settings for any authorization-related fields (API key, feed key, or authentication token) at SimpleCalendar > Settings > Feeds
    Affected if An authorization key or token is stored in the plugin configuration and used for access control decisions

If the plugin is installed with Google Calendar integration enabled and uses an authorization key for access control, the environment may be vulnerable to this authorization bypass.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the SimpleCalendar Google Calendar Events plugin to the latest version which should contain a fix for this authorization bypass. If no update is available, implement additional server-side validation of authorization keys and review access control logic.

Recommended fix Moderate confidence

Version 3.5.10 or latest stable release

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the SimpleCalendar (Google Calendar Events) plugin
  4. 4. Check the current version to confirm it is 3.5.9 or earlier
  5. 5. Update the plugin to the latest available version (3.5.10 or later) by clicking 'Update Now'
  6. 6. After update completes, verify the new version number in the plugins list
  7. 7. Test that calendar events display correctly and that authorization controls work properly
  8. 8. Clear any caching plugins or server-side caches to ensure changes take effect

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68979 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68979 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data