Skip to content
Web

CVE-2026-61962

10.0
Critical
EPSS 0.46%Aug 13, 2026

Unauthenticated remote code execution in WP BASE Booking <= 6.3.0

common questions

Is CVE-2026-61962 being exploited?

Not confirmed. CVE-2026-61962 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.

How severe is CVE-2026-61962?

CVE-2026-61962 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-61962?

Not known from our data. No patch reference has been recorded for CVE-2026-61962, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-61962 affect?

CVE-2026-61962 affects WP BASE Booking plugin <= 6.3.0, WordPress sites using WP BASE Booking. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61962?

Disable/remove plugin immediately or apply vendor patch when available; audit and restore from clean backups.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WP BASE Booking plugin <= 6.3.0WordPress sites using WP BASE Booking
impact

Unauthenticated RCE enabling full site compromise: arbitrary PHP execution, data theft, backdoors and persistent control of WordPress sites.

action required

Immediate action required

affected versions
Hakan Ozevin WP BASE Booking
  • affected<= 6.3.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free