dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-12399

HIGH · 7.2 CVSS v3.1 Published 2025-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Alex Reservations: Smart Restaurant Booking plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the /wp-json/srr/v1/app/upload/file REST endpoint in all versions up to, and including, 2.2.3. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 Alex Reservations WordPress plugin lacks file type validation in its REST API endpoint /wp-json/srr/v1/app/upload/file, allowing authenticated administrators to upload arbitrary files to the server. This unrestricted upload capability enables attackers to upload malicious PHP files and achieve remote code execution.

MitigationUpdate the plugin to version 2.2.4 or later which includes proper file type validation. If unable to update immediately, restrict administrative access and monitor the upload endpoint for suspicious activity.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 Alex Reservations plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Alex Reservations' or check the plugins directory /wp-content/plugins/ for the alex-reservations folder
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    Check the plugin's main PHP file header for the Version comment, or view the plugin details in WordPress admin Plugins page
    Affected if The version is lower than 2.2.4 (or version cannot be determined and the plugin is present)
  3. Check if the vulnerable REST API endpoint is accessible
    Send a GET request to /wp-json/srr/v1/app/upload/file and verify the endpoint responds (even with an error)
    Affected if The endpoint returns a valid REST API response (indicating the plugin's REST routes are registered)
  4. Inspect the plugin's upload directory for unexpected files
    Check /wp-content/uploads/ or the plugin's designated upload folder for recently created .php files or unknown file types
    Affected if Unexpected PHP files or files with double extensions (e.g., image.php.jpg) are found in upload directories

A user is affected if the Alex Reservations plugin is installed with a version before 2.2.4 and the REST endpoint /wp-json/srr/v1/app/upload/file is accessible.

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 2.2.4 or later which includes proper file type validation. If unable to update immediately, restrict administrative access and monitor the upload endpoint for suspicious activity.

Recommended fix Moderate confidence

Latest version after 2.2.3 (check WordPress plugin repository for current safe release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Alex Reservations: Smart Restaurant Booking' plugin
  4. Check if an update is available and install the latest version
  5. If no update is available via the WordPress admin, manually download the latest version from the WordPress plugin repository at plugins.trac.wordpress.org
  6. Deactivate and delete the old version, then upload and activate the new version
  7. Verify the REST endpoint /wp-json/srr/v1/app/upload/file now has proper file type validation

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-2025-12399 — 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-12399 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