dbcve.org
Appointment Booking CalendarWordPress extension · Codepeople

CVE-2025-46241

HIGH · 8.8 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.3.93 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 codepeople Appointment Booking Calendar appointment-booking-calendar allows SQL Injection.This issue affects Appointment Booking Calendar: from n/a through <= 1.3.92.

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

A CSRF vulnerability in the Appointment Booking Calendar plugin (versions <= 1.3.92) allows attackers to craft malicious requests that can lead to SQL injection. The lack of proper CSRF token validation on sensitive actions enables attackers to trick authenticated administrators into executing unintended database commands.

MitigationUpdate to the latest patched version when available. Until then, implement CSRF tokens on all state-changing forms and validate the Referer header. Review and parameterize any database queries that process user-supplied data.

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
Appointment Booking CalendarWordPress extension
Affected:< 1.3.93

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. Check installed plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'Codepeople Appointment Booking Calendar' and compare the version number to 1.3.92
    Affected if The installed version is 1.3.92 or lower
  2. Verify plugin is active
    Confirm the Codepeople Appointment Booking Calendar plugin is currently activated in the WordPress plugins list
    Affected if The plugin is active and version is 1.3.92 or lower
  3. Inspect sensitive action forms for CSRF tokens
    Use browser developer tools or grep the plugin files for form submissions that modify data (such as booking management, settings changes, or calendar configurations). Look for the presence of nonce tokens or CSRF token fields in these forms
    Affected if State-changing forms lack CSRF token validation mechanisms
  4. Check Referer header validation
    Examine the plugin PHP source code for server-side validation of the HTTP Referer header on sensitive actions
    Affected if No Referer header validation is performed before executing database operations

If the plugin is active and the installed version is 1.3.92 or lower without CSRF protections on sensitive actions, the environment is vulnerable to CVE-2025-46241.

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.3.93 or later
Fixed in 1.3.93
Interim mitigation

Update to the latest patched version when available. Until then, implement CSRF tokens on all state-changing forms and validate the Referer header. Review and parameterize any database queries that process user-supplied data.

Recommended fix High confidence

1.3.93

  1. 1. Back up your WordPress database and files before updating
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find 'Appointment Booking Calendar' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.3.93
  5. 5. Alternatively, download version 1.3.93 from the WordPress Plugin Repository or Codepeople's official source
  6. 6. Upload and replace the existing plugin files via Plugins > Add New > Upload Plugin
  7. 7. After update, clear any caching plugins
  8. 8. Test the booking calendar functionality to confirm the plugin works correctly

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

Fix this in Appointment Booking Calendar 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-46241 — 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-46241 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