dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-13454

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 MotoPress Appointment Booking plugin for WordPress is vulnerable to generic SQL Injection via the 's' parameter in all versions up to, and including, 2.4.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with custom-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the mpa_appointment_employee custom role, meaning any user assigned this role can perform the attack.

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

The MotoPress Appointment Booking WordPress plugin fails to properly sanitize the 's' parameter before using it in SQL queries. An authenticated attacker with the mpa_appointment_employee role can inject arbitrary SQL commands by manipulating this parameter, potentially extracting sensitive data from the database.

MitigationUpgrade to a version beyond 2.4.5 when available, and implement proper parameterized queries or sufficient escaping for the 's' parameter in the mean time.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm MotoPress Appointment Booking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'MotoPress Appointment Booking' or check the plugin files in /wp-content/plugins/mp-appointment-booking/ for the main plugin file containing version information
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    Open the main plugin file (typically mp-appointment-booking.php) and locate the 'Version:' header in the plugin comment block, or check the version in the WordPress plugins admin page
    Affected if The installed version is 2.4.5 or lower (versions 2.4.5 and below contain the vulnerability)
  3. Verify the mpa_appointment_employee role exists
    In WordPress admin, go to Users > Roles, or use a role management plugin, or query the wp_roles option in the database to check for the 'mpa_appointment_employee' role
    Affected if The mpa_appointment_employee role exists in the WordPress installation (this role is required for the attack vector)
  4. Inspect access to features using the 's' parameter
    Review the plugin's appointment or employee search functionality that uses the 's' parameter in URL queries (commonly found in admin pages for searching appointments or employees), and confirm this endpoint is accessible to users with the mpa_appointment_employee role
    Affected if The 's' parameter search feature is accessible to authenticated users with the mpa_appointment_employee role

A user is affected if MotoPress Appointment Booking plugin versions 2.4.5 or lower is installed, the mpa_appointment_employee role exists, and that role can access features utilizing the unsanitized 's' parameter in SQL queries.

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 to a version beyond 2.4.5 when available, and implement proper parameterized queries or sufficient escaping for the 's' parameter in the mean time.

Recommended fix Moderate confidence

Version 2.4.6 or later (update to latest available version)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the MotoPress Appointment Booking plugin
  4. Check the current version installed
  5. If the installed version is 2.4.5 or earlier, update the plugin to the latest available version

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-2026-13454 — 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-13454 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