Skip to main content

Booktics EUVDEUVD-2026-97721

| CVE-2026-107418 MEDIUM
Missing Authorization (CWE-862)
2026-10-12 Patchstack GHSA-8jmj-frc2-m8f6
5.4
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege WordPress user
  2. Exploit
    Send crafted request to Booktics endpoint
  3. Execution
    Bypass missing authorization check
  4. Impact
    Read or modify restricted booking data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to possess an authenticated account on the target WordPress site (PR:L), typically any low-privilege role such as subscriber or customer; the affected Booktics plugin (version through 1.0.28) must be installed and active. The flaw is a missing/incorrectly-configured access-control check (CWE-862) on plugin functionality, so no special non-default setting is named in the description - exploitation works against standard installs that permit user registration or that already have low-tier accounts. The primary limiting factor is the authentication requirement: fully unauthenticated visitors cannot exploit it, and impact is confined to limited data read/modification (C:L/I:L), with no availability effect and no user interaction needed.

Impact

This is a moderate, not high-priority, issue. The CVSS 3.1 base score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) describes a network-reachable, low-complexity missing-authorization flaw that nonetheless REQUIRES an authenticated low-privilege account (PR:L) and yields only limited confidentiality and integrity impact with no availability impact - consistent with a typical WordPress broken-access-control bug where a low-level user (e.g., subscriber/customer) can invoke actions reserved for higher roles. No EPSS score was provided in the input, so exploitation probability cannot be quantified here. The CVE is NOT listed in CISA KEV and no public exploit code is referenced, so there is no evidence of active exploitation - the sole reference is a Patchstack advisory. The signals are internally consistent (no CVSS-vs-description conflict): network vector plus PR:L aligns with an authenticated WordPress REST/AJAX authorization gap. Overall this is a genuine but mid-severity authorization weakness whose real-world risk is bounded by the need for a valid account and the low technical impact, not a drop-everything critical.

Exploit ScenarioDerived

An attacker who holds or registers a low-privilege account on a WordPress site running the Booktics plugin (through 1.0.28) sends a crafted request to a plugin endpoint whose authorization check is missing or misconfigured. Because the server does not verify the caller's role, the attacker reads or modifies booking data they should not be able to access. No public proof-of-concept is identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

Missing authorization in the Arraytics Booktics WordPress plugin (versions through 1.0.28) lets an authenticated low-privilege user - such as a subscriber or customer - invoke plugin functionality that should be reserved for higher-privileged roles, resulting in limited unauthorized data disclosure and modification. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, score 5.4) confirms the attack is network-reachable and requires no user interaction, but an account on the target site is a hard prerequisite, and there is no availability impact. No public exploit code has been identified at time of analysis, and this is assessed as a moderate, not high-priority, issue.

RemediationAI

No vendor-released patch or fixed version is identified in the available data, so remediation must start with confirming whether Arraytics has published a Booktics release beyond 1.0.28 and upgrading to it as soon as one is available; track the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/booktics/vulnerability/wordpress-booktics-plugin-1-0-28-broken-access-control-vulnerability-2?_s_id=cve for the version and vendor reference. Until a fix is confirmed, the highest-leverage compensating control is to remove the authentication foothold the flaw depends on: disable open user registration (WordPress Settings > General > Membership) and audit existing accounts so no unnecessary subscriber/customer-level users remain - the trade-off is that legitimate self-service signups stop working. If Booktics is not essential, deactivate and delete the plugin, which eliminates exposure entirely but removes booking functionality. Where the plugin must stay live, restrict access to the affected plugin routes with a WAF or reverse-proxy rule that blocks requests from low-privilege sessions, accepting that rule maintenance and possible false positives are required, and reduce the blast radius of any compromised low-tier account by reviewing role capabilities so subscribers hold no privileges beyond what they need. Because exploitation is limited to Low confidentiality/integrity impact and requires an authenticated account, these measures can be scheduled as routine maintenance rather than treated as an emergency.

Affected VersionsENISA

Booktics 0 ≤1.0.28

Affected Packages

euvd booktics no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-862 (Missing Authorization): a plugin endpoint, AJAX action, or REST route in Booktics fails to perform a capability check (e.g., current_user_can) or nonce/authorization validation before acting on a request, so any account that can reach the route is treated as authorized. This is a WordPress-ecosystem broken-access-control pattern in which the framework supplies the authentication layer but the plugin is responsible for its own capability checks. The CPE cpe:2.3:a:arraytics:booktics:*:*:*:*:*:*:*:* indicates the Arraytics Booktics plugin is affected across all versions up to and including 1.0.28, with no version-range lower bound recorded (from n/a through 1.0.28). The PR:L component of the assessed vector is what limits severity: exploitation is not reachable by anonymous visitors, and the confidentiality and integrity impacts are both rated Low, with no scope change and no availability impact.

Know when Booktics gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

Network-reachable authorization bypass needing a valid low-privilege account (PR:L), no interaction, with limited read/write impact (C:L/I:L) and no availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

Missing Authorization vulnerability in Arraytics Booktics booktics allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booktics: from n/a through 1.0.28.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
niche WordPress booking/appointment plugin, limited install base
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy