dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-6854

HIGH · 7.5 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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
The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'mc_auth' parameter in all versions up to, and including, 3.7.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 · high confidence

The My Calendar WordPress plugin versions up to 3.7.8 contain a time-based blind SQL injection vulnerability in the 'mc_auth' parameter. Unauthenticated attackers can inject arbitrary SQL queries due to insufficient input sanitization and the absence of prepared statements in the existing SQL query, allowing extraction of sensitive database information.

MitigationUpgrade the My Calendar plugin to version 3.7.9 or later which contains the patch. Until then, consider disabling the plugin or implementing a WAF rule to block SQL injection attempts targeting the 'mc_auth' parameter.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Verify My Calendar plugin is installed
    Check for the presence of the My Calendar plugin in your WordPress installation at /wp-content/plugins/my-calendar/ or via WordPress admin dashboard under Plugins
    Affected if Plugin is not installed means not affected
  2. Determine installed My Calendar version
    Read the main plugin file (e.g., my-calendar.php) and look for the 'Version' header in the plugin comment block, or check the WordPress Plugins admin page
    Affected if Version 3.7.8 or lower indicates vulnerability is present; version 3.7.9 or higher means patched
  3. Confirm mc_auth parameter is reachable
    Review plugin code for handling of 'mc_auth' parameter, typically in the main plugin file or authentication-related files, to verify the vulnerable code path exists
    Affected if Code contains direct use of mc_auth parameter in SQL query without prepared statements indicates exploitable condition
  4. Check if WordPress is publicly accessible
    Determine if the WordPress site is exposed to the internet (check firewall, network settings, or access logs for external requests)
    Affected if Publicly accessible sites with vulnerable plugin version are directly exploitable without authentication

You are affected if My Calendar plugin version 3.7.8 or lower is installed and the site is accessible, since the vulnerability allows unauthenticated SQL injection via the mc_auth parameter.

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

Upgrade the My Calendar plugin to version 3.7.9 or later which contains the patch. Until then, consider disabling the plugin or implementing a WAF rule to block SQL injection attempts targeting the 'mc_auth' parameter.

Recommended fix Moderate confidence

Version 3.7.9 or later

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Locate 'My Calendar – Accessible Event Manager' in the plugin list
  3. Check the current installed version (should be 3.7.8 or earlier if still vulnerable)
  4. Click 'Update now' if an update is available, or manually download version 3.7.9 or later from wordpress.org/plugins/my-calendar/
  5. After updating, verify the new version number reflects 3.7.9 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6854 — 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-2026-6854 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