Skip to main content
Menu
CVEs

Alejandro Alex Reservations unauthenticated SQL injection in WordPress plugin

CVE-2026-124415EUVD-2026-125429GHSA-M2X2-RCGP-H6J7Published November 13, 2026, updated

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 2.4.9
Who is exposed
Not reported

Summary

The Alex Reservations plugin for WordPress, by Alejandro, contains an SQL injection flaw that lets an attacker read or tamper with the site's database. It can be reached remotely over the network, without logging in or any action by a user.

Written by a model

Original description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Alejandro Alex Reservations alex-reservations allows SQL Injection.This issue affects Alex Reservations: from n/a through 2.4.8.

Who should check

Teams running the Alex Reservations WordPress plugin version 2.4.8 or earlier on their WordPress sites.

“WordPress Alex Reservations Plugin <= 2.4.8 is vulnerable to a high priority SQL Injection”

patchstack.com

What to do

Upgrade to a fixed version: 2.4.9.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-124415 (WordPress Alex Reservations plugin <= 2.4.8 - SQL Injection vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124415 (entry last updated 2026-11-13):
Affected:
- Alejandro Alex Reservations: fixed in 2.4.9
Fixed versions: 2.4.9.
Conditions (all must be true for the bug to be hit):
- Alex Reservations WordPress plugin version 2.4.8 or earlier (source: https://patchstack.com/database/wordpress/plugin/alex-reservations/vulnerability/wordpress-alex-reservations-plugin-2-4-8-sql-injection-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-124415 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124415 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/alex-reservations/vulnerability/wordpress-alex-reservations-plugin-2-4-8-sql-injection-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-124415
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124415
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124415"}.

Affected versions

cve.now Index

29of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 13Nov 22
  • EPSS: 0.32%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

Questions about CVE-2026-124415

Is CVE-2026-124415 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The Alex Reservations WordPress plugin has an SQL injection flaw, which lets an attacker run database queries through the plugin. According to the facts, an attacker could read, modify, or delete the entire database, including user accounts and private data.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-124415?

alex-reservations: through 2.4.8 (fixed in 2.4.9).

Source: cve.now feed data

Am I affected, and how do I check?

Alex Reservations plugin version 2.4.8 and earlier are affected. To check a site, look at the plugin version shown on the WordPress Plugins page or in the plugin's details in the admin dashboard.

Source: patchstack.com, cve.org

How do I fix CVE-2026-124415?

Update the Alex Reservations plugin to version 2.4.9 or later, the fixed version named in the advisory. The advisory asks for the latest available version, which is at least 2.4.9.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.