dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13754

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-19
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
The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.6.9.16. This is due to the plugin exposing its admin embed endpoint at `/wp-json/ssa/v1/embed-inner-admin` without authentication, which leaks plugin settings including staff names, business names, and configuration data that are not publicly displayed on the booking form. This makes it possible for unauthenticated attackers to extract private business configuration. In premium versions with integrations configured, this might also expose other sensitive data including API keys for external services.

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 Simply Schedule Appointments WordPress plugin exposes an admin API endpoint at `/wp-json/ssa/v1/embed-inner-admin` without requiring authentication. This endpoint returns private plugin configuration including staff names, business details, and settings not intended for public display. In premium versions, integrated third-party service API keys may also be exposed.

MitigationUpdate the plugin to version 1.6.9.17 or later which adds authentication requirements to the embed endpoint. Until patched, monitor access logs for unauthorized requests to the exposed endpoint.

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. Verify Simply Schedule Appointments plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder containing 'simply-schedule-appointments'
    Affected if The plugin appears in the list of installed plugins
  2. Check the installed plugin version
    In WordPress admin, click on the plugin to view its details and note the version number, or open the main plugin file (e.g., simply-schedule-appointments.php) and look for the Version header in the plugin comments
    Affected if The version number is lower than 1.6.9.17 or cannot be determined (unlisted)
  3. Test the exposed endpoint for unauthenticated access
    Send a GET request to your site at /wp-json/ssa/v1/embed-inner-admin (e.g., using curl: curl -s https://yourdomain.com/wp-json/ssa/v1/embed-inner-admin) without providing any authentication tokens
    Affected if The endpoint returns an HTTP 200 response with JSON data containing staff names, business details, or configuration settings
  4. Inspect the endpoint response for sensitive data
    Examine the JSON response from the previous step for any of the following: staff member names, business/organization names, address or contact details, internal settings, or in premium versions, API keys for third-party services (such as Google Calendar, Zoom, payment gateways)
    Affected if The response contains any staff names, business details, settings, or API keys not intended for public exposure

You are affected if the Simply Schedule Appointments plugin is installed with a version below 1.6.9.17 and the /wp-json/ssa/v1/embed-inner-admin endpoint returns sensitive configuration data without requiring authentication.

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 plugin to version 1.6.9.17 or later which adds authentication requirements to the embed endpoint. Until patched, monitor access logs for unauthorized requests to the exposed endpoint.

Recommended fix High confidence

1.6.9.17 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Simply Schedule Appointments' plugin
  4. 4. If an update is available, click 'Update Now' to update to version 1.6.9.17 or later
  5. 5. Verify the update completed successfully
  6. 6. Test that the booking functionality still works correctly

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

Have this fixed 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 help mitigating

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-13754 — 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-13754 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