dbcve.org
Simple Calendar For ElementorWordPress extension · Migaweb

CVE-2025-46249

HIGH · 8.8 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.6.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Michael Simple calendar for Elementor simple-calendar-for-elementor allows Cross Site Request Forgery.This issue affects Simple calendar for Elementor: from n/a through <= 1.6.4.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Simple calendar for Elementor WordPress plugin allows attackers to trick authenticated users into performing unintended actions via maliciously crafted requests. The plugin lacks proper CSRF token validation on sensitive operations, enabling attackers to potentially modify calendar data or configurations on behalf of logged-in administrators.

MitigationImplement anti-CSRF tokens (nonces) for all state-changing actions and verify the nonce on form submissions and AJAX requests. Additionally, enforce SameSite cookie attributes and validate the Origin/Referer headers.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simple Calendar For ElementorWordPress extension
Affected:< 1.6.5

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the Simple Calendar for Elementor plugin
    Check your WordPress installation under wp-content/plugins/ for a folder named 'simple-calendar-for-elementor' or similar variant (check common paths: wp-content/plugins/miga-simple-calendar-for-elementor or similar naming)
    Affected if The plugin folder exists in your WordPress plugins directory
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Migaweb Simple Calendar For Elementor' or check the version in the plugin's main PHP file header (usually in the plugin folder root)
    Affected if The displayed version is 1.6.4 or lower (any version below 1.6.5)
  3. Verify plugin status
    Confirm the plugin is active by checking the 'Active' status in WordPress Plugins page
    Affected if The plugin is installed and active (CSRF affects authenticated admin sessions, so even if inactive the vulnerable code exists but is not exposed)
  4. Confirm WordPress user role exposure
    Review if any administrator-level users exist in your WordPress users panel
    Affected if Administrator accounts exist (the CSRF targets authenticated administrators performing state-changing actions)

You are affected if the Migaweb Simple Calendar For Elementor plugin version is 1.6.4 or lower and the plugin is installed on your WordPress site.

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
Upgrade available Upgrade to 1.6.5 or later
Fixed in 1.6.5
Interim mitigation

Implement anti-CSRF tokens (nonces) for all state-changing actions and verify the nonce on form submissions and AJAX requests. Additionally, enforce SameSite cookie attributes and validate the Origin/Referer headers.

Recommended fix Moderate confidence

Simple Calendar For Elementor version 1.6.5

  1. 1. Create a complete backup of your WordPress site (database and files) before making any changes
  2. 2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. 3. Find 'Simple Calendar For Elementor' in the plugin list
  4. 4. Click 'Update Now' if an update is available, or manually update to version 1.6.5
  5. 5. After updating, clear any caching plugins or server-side caches
  6. 6. Verify the plugin shows version 1.6.5 as the installed version
  7. 7. Test calendar functionality to ensure the update did not break existing features

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

Fix this in Simple Calendar For Elementor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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