Skip to main content

Tourfic Pro CVE-2026-39774

| EUVDEUVD-2026-93024 HIGH
Incorrect Privilege Assignment (CWE-266)
2026-10-06 Patchstack GHSA-xc6p-j8fv-7vx2
8.8
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. Delivery
    Send crafted request to Tourfic Pro endpoint
  3. Exploit
    Trigger incorrect privilege assignment (CWE-266)
  4. Execution
    Escalate to administrator
  5. Impact
    Full site compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
Exploitation Conditions

The target must run the Tourfic Pro plugin (the paid extension of the Tourfic travel/hotel booking plugin) at version 1.17.3 or earlier on WordPress, reachable over the network. Per the CVSS vector (PR:L), the attacker needs a low-privilege authenticated account (e.g., a self-registered subscriber), and no user interaction is required (UI:N). LIMITING FACTOR AND CONFLICT: the vendor description instead calls this 'Unauthenticated,' which would remove the account prerequisite entirely; defenders should verify whether open user registration or an unauthenticated endpoint is the true precondition, as this determines whether every visitor or only registered users can exploit it. Exploitation is further bounded by the plugin's limited installed base.

Impact

This is a credible priority for any site running the affected plugin, but the signals are incomplete and internally conflicting. The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N) reflects network-reachable, low-complexity exploitation with high confidentiality, integrity and availability impact - consistent with a privilege-escalation flaw (CWE-266) that lets a low-privileged WordPress account gain administrator control. However, there is a direct conflict: the description labels this 'Unauthenticated Privilege Escalation' while the CVSS vector specifies PR:L (authenticated, low privileges). These cannot both be literally true - if exploitation is truly unauthenticated the vector should read PR:N - so the real attack surface (any visitor vs. any registered subscriber) must be verified with Patchstack/vendor before final triage. No EPSS score, no CISA KEV listing, and no public exploit (POC) were provided, so there is no evidence of active exploitation or weaponization; the elevated score is driven entirely by the CVSS impact/exploitability metrics rather than observed real-world attack telemetry. Net: treat as a high-severity patch-soon item for exposed Tourfic Pro installs, but note the risk is bounded by the plugin's limited deployment footprint and by the unresolved authentication question.

Exploit ScenarioDerived

An attacker with (per the CVSS vector) a low-privileged account on a WordPress site running Tourfic Pro <= 1.17.3 sends a crafted request to a vulnerable plugin endpoint that incorrectly assigns privileges, elevating the account to administrator. If the vendor's 'unauthenticated' labeling is accurate, this could instead be performed with no account at all. No public exploit code was identified at time of analysis, and low attack complexity (AC:L) means exploitation would be reliable once the request format is known.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.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 06, 2026

Privilege escalation in the WordPress plugin Tourfic Pro (the paid extension of the Tourfic travel and hotel booking plugin) at version 1.17.3 and earlier allows an attacker to elevate to a higher-privileged WordPress role, with a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflecting full loss of confidentiality, integrity and availability within the affected site. The CVSS vector's PR:L indicates the attacker must first hold a low-privilege authenticated account (for example a self-registered subscriber) and that no user interaction is required, but the vendor's own description labels the flaw 'Unauthenticated' - a material conflict that determines whether only registered users or any site visitor can trigger it, and defenders should verify which precondition actually applies. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV; the plugin's comparatively small installed base further limits real-world exposure, so this is best treated as a credible priority for sites running the plugin rather than a broadly exploited campaign.

RemediationAI

No vendor-released patch version is identified in the available data: the only supplied reference is the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/tourfic-pro/vulnerability/wordpress-tourfic-pro-plugin-1-17-3-privilege-escalation-vulnerability?_s_id=cve), which documents the flaw as affecting 1.17.3 and earlier but does not give a fixed version here, so check the vendor's Tourfic Pro changelog and update to the first release that is later than 1.17.3 as soon as it is confirmed to contain the fix - treat any such version only when it is verifiable against the vendor's own changelog rather than assumed. Until a patched release is confirmed and deployed, apply targeted compensating controls: if the site's user registration is open, restrict or disable new subscriber self-registration (this directly removes the PR:L foothold in the CVSS reading of the flaw, at the cost of blocking legitimate sign-ups), and if the vendor description's 'Unauthenticated' claim proves accurate it will not be sufficient, so additionally block or CAPTCHA the plugin's front-end booking and account endpoints and review roles/capabilities assigned through the plugin to ensure no subscriber-level user has acquired elevated capabilities. Harden in depth by enforcing least privilege for booking-management capabilities, monitoring for unexpected administrator-role grants and new admin accounts, auditing existing users for unauthorised role changes, and, if the plugin cannot be updated promptly, temporarily deactivating Tourfic Pro - which stops the attack path but also removes all booking functionality from the site. Given the unresolved unauthenticated-versus-authenticated conflict, prioritise confirming the true precondition on your own deployment before deciding how aggressively to lock down registration and endpoints.

Affected VersionsENISA

Tourfic Pro n/a ≤1.17.3

Affected Packages

euvd tourfic_pro 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

This is a CWE-266 (Incorrect Privilege Assignment) flaw in the Tourfic Pro WordPress plugin, meaning the plugin grants or assigns a privilege level to a user or action without properly verifying that the caller is entitled to it. The vulnerable code path is reached over the network (AV:N) against a WordPress installation with the plugin active; WordPress role/capability handling is the underlying trust boundary, and an incorrect assignment or missing capability check on a plugin action lets a caller obtain capabilities they should not hold. The CPE record cpe:2.3:a:tourfic_ai_studio:tourfic_pro:*:*:*:*:*:*:*:* identifies the affected vendor product as Tourfic AI Studio's Tourfic Pro, the commercial extension layered on top of the free Tourfic booking plugin, and the wildcarded version field is consistent with the advisory covering all releases up to and including 1.17.3. The CVSS vector's PR:L and the vendor's 'Unauthenticated' wording describe two different preconditions: a low-privileged but registered account (which is what PR:L encodes) versus no account at all. Reconciling that difference requires checking whether the vulnerable endpoint enforces a nonce, capability check, or role gate - if it does not, the practical precondition collapses toward unauthenticated exploitation via open registration or a directly reachable action, which is the higher-risk reading.

Know when Tourfic Pro 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 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable low-complexity privilege escalation; PR:L retained because the CVSS vector indicates a low-privilege account despite the 'unauthenticated' title, and admin takeover yields full C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated Privilege Escalation in Tourfic Pro <= 1.17.3 versions.

Executive ViewAI

Why It Matters

Tourfic Pro, the paid WordPress booking plugin, contains a high-severity privilege escalation vulnerability (CVE-2026-39774) in versions 1.17.3 and earlier, allowing an attacker to elevate to a higher-privileged WordPress role and gain full control over the affected site's confidentiality, integrity, and availability. Organizations using this plugin for travel and hotel bookings face potential data theft, site defacement, or operational disruption; the CVSS vector requires a low-privilege authenticated account, though the vendor description labels the flaw unauthenticated, so defenders should verify the true precondition. With no vendor patch available and no public exploit identified at time of analysis, leadership should prioritize verifying exposure and implementing interim mitigations while monitoring for updates.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include disabling the plugin, restricting low-privilege account creation, enforcing least privilege, deploying WAF rules to detect privilege escalation attempts, monitoring WordPress role changes, and conducting regular user account audits.

Threat Intelligence Overview

EPSS Score
0.2%
Top 85% exploitable
Prevalence
Low
paid add-on for a niche WordPress travel/hotel booking plugin
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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

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