CVE-2025-1119
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 · uneditedThe Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.6.8.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
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 confidenceThe Simply Schedule Appointments WordPress plugin versions up to 1.6.8.5 fails to validate a user-supplied value before passing it to the do_shortcode() function, allowing unauthenticated attackers to execute arbitrary shortcodes on the WordPress site.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Simply Schedule Appointments pluginCheck the wp-content/plugins/ directory for a folder named 'simply-schedule-appointments'. Common paths include wp-content/plugins/simply-schedule-appointments/simply-schedule-appointments.phpAffected if The plugin folder exists in the WordPress plugins directory
-
Read the installed version from the plugin headerOpen the main plugin PHP file and locate the plugin comment header at the top. The 'Version:' field contains the installed version number (for example: Version: 1.6.8.5)Affected if The version read is 1.6.8.5 or any version lower than 1.6.8.5
-
Verify the plugin is currently activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and check if Simply Schedule Appointments shows as 'Active', or query the wp_options table for the active_plugins option containing the plugin slugAffected if The plugin is enabled and shows as active in WordPress
-
Confirm shortcode functionality is in useThe vulnerability affects any WordPress site where the plugin shortcode functionality is loaded. Check if the plugin provides shortcodes (commonly [simply-schedule-appointments] or similar) by viewing the plugin documentation or testing a shortcode on the siteAffected if The plugin shortcodes are available or being used on the site
The environment is affected if Simply Schedule Appointments plugin version 1.6.8.5 or lower is installed AND the plugin is active on the WordPress site
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to a version newer than 1.6.8.5 when available, or disable the plugin until a patched version is released.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1119 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1119 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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