Skip to main content
VulnerabilityPublished

CVE-2026-104012: Rox Appointment Booking (WordPress plugin) · Improper Privilege Management

Affects Rox Appointment Booking (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 31 Oct 2026, 08:10 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.18.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
roxnorRox Appointment Booking – Event, Calendar & Appointment SchedulingAffected
  • <=1.3.1
Fixed in–

AI-suggested

Administrators should avoid opening or updating customer records received from untrusted sources until a fix is available. Monitor vendor advisories for updates. Consider restricting access to the REST endpoint or disabling the plugin if feasible until remediation is provided.

Description

The Rox Appointment Booking plugin for WordPress up to version 1.3.1 contains a privilege escalation vulnerability via mass assignment. An unauthenticated attacker can inject an arbitrary WordPress user ID into a customer record through a public REST endpoint. If an administrator later opens and updates this poisoned record, the attacker's supplied user ID and email are used to update the administrator's account, enabling full account takeover via password reset. Exploitation requires the attacker to know or guess a valid administrator user ID and for an administrator to interact with the malicious record.

References

Community reviews

Loading reviews…