dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4668

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-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

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 Booking for Appointments and Events Calendar - Amelia plugin for WordPress is vulnerable to SQL Injection via the `sort` parameter in the payments listing endpoint in all versions up to, and including, 2.1.2. This is due to insufficient escaping on the user-supplied `sort` parameter and lack of sufficient preparation on the existing SQL query in `PaymentRepository.php`, where the sort field is interpolated directly into an ORDER BY clause without sanitization or whitelist validation. PDO prepared statements do not protect ORDER BY column names. GET requests also skip Amelia's nonce validation entirely. This makes it possible for authenticated attackers, with Manager-level (`wpamelia-manager`) access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database via time-based blind SQL injection.

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

SQL injection in Amelia WordPress plugin's payment listing endpoint where the `sort` parameter is directly interpolated into an ORDER BY clause in `PaymentRepository.php` without sanitization or whitelist validation. PDO prepared statements do not protect column names in ORDER BY clauses. Authenticated attackers with Manager-level access can exploit GET requests (which bypass nonce validation) to perform time-based blind SQL injection and extract sensitive database information.

MitigationUpgrade to a patched version that implements proper whitelist validation or parameterized column names for the sort parameter. Until then, restrict the `wpamelia-manager` role to trusted users only.

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 Amelia plugin is installed
    Check the WordPress plugins directory for the Amelia plugin folder, or query the wp_plugins table for 'Amelia' or 'amelia' in the plugin name.
    Affected if The Amelia plugin is active on the WordPress site.
  2. Identify installed Amelia version
    Read the main plugin file (typically wp-content/plugins/amelia-booking/wpamelia.php or wp-content/plugins/amelia-booking/amelia-booking.php) and locate the Version header, or query wp_options for option_name='wpamelia_version' or similar.
    Affected if The installed version matches or falls within the vulnerable version range for this CVE.
  3. Verify Manager role users exist
    Query the wp_usermeta table for meta_key='wp_capabilities' containing 'amelia-manager' or 'wpamelia-manager', or use WP-CLI: wp user list --role=amelia-manager
    Affected if There is at least one user with Manager-level access in Amelia (wpamelia-manager role).
  4. Confirm vulnerable endpoint is accessible
    Test a GET request to the Amelia API endpoint (typically /wp-json/wpamelia/v1/payments?sort[]=anything) to verify the endpoint accepts the sort parameter without authentication block for authenticated managers.
    Affected if The endpoint responds and accepts the sort parameter for Manager-level authenticated requests.
  5. Inspect PaymentRepository.php for vulnerable code
    Locate the PaymentRepository.php file in the plugin (wp-content/plugins/amelia-booking/src/Repositories/PaymentRepository.php) and search for the sort parameter handling in ORDER BY clauses without whitelist validation or prepared statement usage for column names.
    Affected if The code directly interpolates the sort parameter into ORDER BY without sanitization.

A user is affected if they have Amelia plugin installed with a vulnerable version AND have at least one user with the wpamelia-manager role, as the exploit requires Manager-level 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

Upgrade to a patched version that implements proper whitelist validation or parameterized column names for the sort parameter. Until then, restrict the `wpamelia-manager` role to trusted users only.

Recommended fix Moderate confidence

Amelia plugin version 2.1.3 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the Amelia plugin
  4. Check the current version (should be 2.1.2 or below)
  5. Click 'Update Now' if a newer version is available, or manually download the latest version from wordpress.org/plugins/amelia
  6. After updating, verify the version number shows the patched release

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 / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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