---
title: "CVE-2026-104012: Rox Appointment Booking - Privilege Escalation"
description: "Rox Appointment Booking WordPress plugin <= 1.3.1 contains a privilege escalation via mass assignment in the public REST endpoint, letting unauthenticated attackers persist arbitrary wp_user_id and email, exploit requires an administrator to open and save the poisoned customer record."
url: https://panop.io/threat-heartbeat/CVE-2026-104012/
---

# CVE-2026-104012 Rox Appointment Booking - Privilege Escalation

Rox Appointment Booking WordPress plugin <= 1.3.1 contains a privilege escalation via mass assignment in the public REST endpoint, letting unauthenticated attackers persist arbitrary wp\_user\_id and email, exploit requires an administrator to open and save the poisoned customer record.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.28% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-104012)

## Details

Type

Privilege Escalation

Impact

Privilege Escalation

CVSS vector

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

Published

31 October 2026

Updated

1 November 2026

Weakness

[CWE-269](https://cwe.mitre.org/data/definitions/269.html)

## Vendor fix

Update to the latest version beyond 1.3.1.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-104012](https://nvd.nist.gov/vuln/detail/CVE-2026-104012)
- [https://downloads.wordpress.org/plugin/rox-appointment-booking.1.3.2.zip](https://downloads.wordpress.org/plugin/rox-appointment-booking.1.3.2.zip)
- [https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/Customer/Data/CustomerModel.php#L38](https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/Customer/Data/CustomerModel.php#L38)
- [https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/Customer/REST/SaveCustomer.php#L262](https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/Customer/REST/SaveCustomer.php#L262)
- [https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/FrontendBookingPanel/REST/BookingConfirm.php#L61](https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/FrontendBookingPanel/REST/BookingConfirm.php#L61)
- [https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/FrontendBookingPanel/Services/CustomerService.php#L74](https://plugins.trac.wordpress.org/browser/rox-appointment-booking/tags/1.3.0/src/Modules/FrontendBookingPanel/Services/CustomerService.php#L74)
- [https://www.wordfence.com/threat-intel/vulnerabilities/id/2a32f428-fa6e-469b-b004-e80a1029af80?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/2a32f428-fa6e-469b-b004-e80a1029af80?source=cve)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)