CVE-2025-12788

Published

11 November 2025

Modified

15 April 2026

CVSS Score v3.1 5.3

Click a component to see what it means

Raw vector

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

EPSS Score 0.0033 25th percentile

Risk Priority 43 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-12788 is a medium-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Wordpress (inferred from references). Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2025-84360

Vulnerability Data

The Hydra Booking — Appointment Scheduling & Booking Calendar plugin for WordPress is vulnerable to missing payment verification to unauthenticated payment bypass in all versions up to, and including, 1.1.27. This is due to the plugin accepting client-controlled payment confirmation…

data in the tfhb_meeting_paypal_payment_confirmation_callback function without server-side verification with PayPal's API. This makes it possible for unauthenticated attackers to bypass payment requirements and confirm bookings as paid without any actual payment transaction occurring.

CWE(s): CWE-602

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-52008Shared CWE-602

CVE-2026-13919Shared CWE-602

CVE-2026-13930Shared CWE-602

CVE-2026-39415Shared CWE-602

CVE-2025-25497Shared CWE-602

CVE-2026-13896Shared CWE-602

CVE-2025-20113Shared CWE-602

CVE-2025-61197Shared CWE-602

CVE-2026-59504Shared CWE-602

CVE-2026-64813Shared CWE-602

Affected Assets

Wordpress

—

inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V10.7.1
V2.2.2
V8.3.1
V10.4.1

Mitigating Controls (NIST 800-53 r5) AI

AC-25 Reference Monitor good match

Requires a tamper-proof, always-invoked reference monitor that cannot be bypassed by client-side logic.

AC-3 Access Enforcement good match

Enforces all access decisions on the server according to policy rather than trusting client-supplied enforcement.

AC-4 Information Flow Enforcement good match

Enforces information-flow rules at the server boundary instead of delegating them to the client.

SC-7 Boundary Protection partial match

Monitors and controls all external and key internal interfaces so that server-side policy cannot be off-loaded to clients.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly prevent design flaws that place server security enforcement on the client.

PR.AA-05 partial match

prevents

Proper policy-based enforcement of authorizations implies server-side controls rather than client-only checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.27 Secure system architecture and engineering principles mostly match

prevents

Secure architecture principles discourage client-side trust but do not directly address this weakness.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect client-side enforcement but is not the primary mitigation.

A.8.3 Information access restriction mostly match

prevents

Information access restriction is undermined when the client is trusted to enforce it.

A.8.25 Secure development life cycle partial match

prevents

Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.

A.8.26 Application security requirements partial match

prevents

Application security requirements explicitly call for server-side enforcement of security mechanisms.

A.8.28 Secure coding partial match

prevents

Secure coding standards require server-side checks and reject client-only enforcement.