dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-12482

HIGH · 7.5 CVSS v3.1 Published 2025-11-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to SQL Injection via the ‘search’ parameter in all versions up to, and including, 1.2.35 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Amelia WordPress plugin versions up to 1.2.35 contain an unauthenticated SQL Injection vulnerability in the 'search' parameter. The plugin fails to properly escape user-supplied input and does not use prepared statements when constructing SQL queries, allowing attackers to inject arbitrary SQL commands to exfiltrate database contents.

MitigationUpdate the Amelia plugin to version 1.2.36 or later. As a temporary mitigation, deploy a WAF rule to block SQL injection patterns in the 'search' parameter until the update can be applied.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate Amelia plugin installation
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and find the Amelia plugin entry. Note the version number displayed. Alternatively, inspect the plugin file header in wp-content/plugins/amelia/amelia.php
    Affected if The Amelia plugin is installed and the displayed version is 1.2.35 or lower
  2. Verify plugin version against vulnerable range
    Compare the installed version number to the affected range. Amelia plugin versions 1.2.35 and below are vulnerable. Versions 1.2.36 and later contain the fix.
    Affected if The installed version is 1.2.35 or any earlier version (e.g., 1.2.34, 1.2.0, etc.)
  3. Identify vulnerable search functionality
    Inspect the plugin files for the search parameter handler. Look for PHP files in the Amelia plugin directory that process a 'search' parameter in HTTP requests without using prepared statements. Common locations include ajax handlers or API endpoints.
    Affected if The plugin processes a 'search' parameter using direct string concatenation in SQL queries instead of prepared statements
  4. Confirm unauthenticated access to vulnerable endpoint
    Test whether the endpoint accepting the 'search' parameter is accessible without authentication. Attempt a request to common Amelia booking/search endpoints without providing login credentials.
    Affected if The search functionality is accessible to unauthenticated users (no login required)
  5. Check for SQL injection indicators in logs
    Review web server access logs and WordPress debug logs for suspicious patterns in 'search' parameters, such as SQL keywords (UNION, SELECT, SLEEP) or unusual encoding that may indicate injection attempts.
    Affected if Suspicious SQL injection patterns appear in logs for the 'search' parameter pointing to Amelia endpoints

A WordPress environment is affected if the Amelia plugin is installed with version 1.2.35 or earlier and the plugin's search functionality is accessible (which is unauthenticated by default).

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 Amelia plugin to version 1.2.36 or later. As a temporary mitigation, deploy a WAF rule to block SQL injection patterns in the 'search' parameter until the update can be applied.

Recommended fix High confidence

Amelia plugin version 1.2.36 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Amelia – Booking for Appointments and Events Calendar' plugin
  4. Click 'Update Now' if an update is available, or manually download version 1.2.36 or higher from the WordPress plugin repository
  5. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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