Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-104012— Rox Appointment Booking <= 1.3.1 - Unauthenticated Privilege Escalation via Mass Assignment to Mass Assignment via '/public/booking' Endpoint

Quick assessment

Affected
roxnor Rox Appointment Booking – Event, Calendar & Appointment Scheduling
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

WordPress 插件"Rox Appointment Booking – Appointment Booking Scheduling Solution"在 1.3.1 及之前的所有版本中，存在通过批量赋值（Mass Assignment）导致的权限提升漏洞。该漏洞源于公开的 REST API 端点 在创建新客户记录时，直接将请求体中的原始数据批量赋值到数据库，而 属性中包含了内部字段 。这使得未认证的攻击者能够在未进行任何授权检查的情况下，将任意 WordPress 用户 ID 与攻击者控制的邮箱地址绑定并持

CVSS 8.8 · High EPSS 0.28% · P21

Affected Version Matrix 1

VendorProduct Version RangeStatus
roxnor Rox Appointment Booking – Event, Calendar & Appointment Scheduling ≤ 1.3.1 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-104012

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Rox Appointment Booking <= 1.3.1 - Unauthenticated Privilege Escalation via Mass Assignment to Mass Assignment via '/public/booking' Endpoint
Source: CVE Program / CVE List V5
Vulnerability Description
The Rox Appointment Booking – Appointment Booking Scheduling Solution plugin for WordPress is vulnerable to Privilege Escalation via Mass Assignment in all versions up to, and including, 1.3.1 This is due to the public `/rox-appointment-booking/v1/public/booking` REST endpoint performing mass-assignment of the raw request body into a new customer row while `CustomerModel::$fillable` includes the internal `wp_user_id` column, allowing an unauthenticated attacker to persist an arbitrary WordPress user ID alongside an attacker-controlled email address with no authorization check. When an administrator subsequently opens the poisoned customer record and clicks Update Customer, `SaveCustomer::handleRequest()` passes the stored `wp_user_id` and attacker-supplied email to `wp_update_user()` — succeeding because `LinkedAccount::canChange()` unconditionally returns true when the acting user holds the `edit_users` capability — thereby overwriting the targeted administrator's email address and enabling full account takeover via a standard WordPress password-reset request. Successful exploitation requires an administrator to open and save the poisoned record, and the attacker must know or guess a valid administrator user ID (such as the default user ID 1).
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
特权管理不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
roxnor Rox Appointment Booking – Event, Calendar & Appointment Scheduling 0 ~ 1.3.1 -

II. Public POCs for CVE-2026-104012

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-104012

请登录查看更多情报信息。

Other References for CVE-2026-104012 (6)

IV. Related Vulnerabilities

Same vendor: roxnor
Same weakness: CWE-269