Skip to main content

Estatik EUVDEUVD-2026-89863

| CVE-2026-96350 CRITICAL
Incorrect Privilege Assignment (CWE-266)
2026-09-30 Patchstack GHSA-p7cm-9j6f-99xv
9.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Register/authenticate as Subscriber
  2. Delivery
    Invoke vulnerable privilege-assignment endpoint
  3. Exploit
    Elevate own account role/capabilities
  4. Execution
    Gain administrative control
  5. Impact
    Compromise site content and data

Vulnerability Assessment

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

Requires the Estatik plugin (version 4.3.5 or earlier) installed on a WordPress site, and - per the 'Subscriber Privilege Escalation' description - an authenticated low-privileged Subscriber account, which is trivially obtainable where open user registration is enabled (common on real-estate/listing sites). The limiting factor is this authentication prerequisite: despite the published vector's PR:N, the description indicates a Subscriber-level account is needed, so exploitation is not truly anonymous. No user interaction by a victim is required. No non-default server configuration is indicated beyond having the vulnerable plugin active.

Impact

The headline CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), which on its face signals a critical, remote, unauthenticated compromise. However, there is a clear internal conflict: the description explicitly labels this a 'Subscriber Privilege Escalation,' which means an attacker must already hold a low-privileged authenticated Subscriber account - that is inconsistent with the PR:N (no privileges required) in the published vector. This mismatch strongly suggests the true privilege requirement is PR:L, which would reduce the realistic base score to roughly 8.8. CWE-266 (Incorrect Privilege Assignment) is consistent with a Subscriber being able to elevate to a higher role (e.g., editor/admin-equivalent), which for a WordPress plugin can effectively lead to full site takeover. On real-world signals: there is no EPSS score, no CISA KEV listing, and no public proof-of-concept referenced - the only source is a single Patchstack advisory. There is no SSVC decision data provided. Net assessment: this is a genuinely serious flaw because privilege escalation on WordPress often chains to full compromise, but the 'unauthenticated CVSS 9.8' framing likely overstates it - realistic risk is high-but-gated-by-an-account, and the low-confidence single-source, no-exploit posture argues for prompt patching rather than emergency treatment. Verify the actual privilege prerequisite with the vendor advisory before treating this as unauthenticated.

Exploit ScenarioDerived

An attacker registers a low-privileged Subscriber account on a WordPress site running Estatik <= 4.3.5 (open registration is common on real-estate listing sites), then abuses an insecure privilege-assignment code path to grant their own account elevated capabilities. With an elevated role they can manipulate content, plugin settings, or user roles, plausibly escalating to full administrative control of the site. No public exploit code is referenced at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.5% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 30, 2026

Privilege escalation in the Estatik WordPress plugin (versions through 4.3.5) allows an authenticated Subscriber-level account to elevate its privileges to higher roles, potentially achieving full site compromise. Although the published CVSS 3.1 vector lists PR:N (score 9.8), the independent assessment and the 'Subscriber Privilege Escalation' description confirm that a Subscriber account is required; such an account is trivially obtainable when open user registration is enabled, common on real-estate or listing sites. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.

RemediationAI

Update the Estatik plugin to the latest version beyond 4.3.5; consult the Patchstack advisory for the exact patched release, as no specific fixed version is confirmed in the provided data. If immediate upgrade is not possible, consider temporarily deactivating the Estatik plugin, accepting the trade-off of losing real-estate listing functionality, or disabling open user registration in WordPress (Settings > General > Membership) to prevent attackers from obtaining the prerequisite Subscriber account - though this does not fix the underlying escalation logic and may disrupt legitimate onboarding. Additionally, restrict Subscriber capabilities, audit user roles for unexpected administrative assignments, monitor logs for privilege-change events, and apply virtual patching or WAF rules if available from your security provider.

Affected VersionsENISA

Estatik n/a ≤4.3.5

Affected Packages

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

Estatik is a WordPress plugin used for real-estate and property-listing functionality. The vulnerability is classified as CWE-266 (Incorrect Privilege Assignment): the plugin fails to properly enforce role or capability checks before performing privileged actions, allowing a low-privileged Subscriber to invoke functionality that should be restricted to higher roles. This typically manifests in AJAX actions, REST API endpoints, or form handlers that trust client-supplied input or lack nonce/capability verification. The affected component is captured by the CPE cpe:2.3:a:estatik:estatik:*:*:*:*:*:*:*:*, with all plugin versions up to 4.3.5 in scope. The published CVSS vector reports PR:N, but the description and independent assessment indicate a Subscriber account (PR:L) is needed, so exploitation is not anonymous; an attacker must first authenticate, which is easy if open registration is enabled. No non-default server configuration beyond an active vulnerable plugin is indicated.

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

Description states a Subscriber account is required, so PR:L (not PR:N); privilege escalation yields full role control giving high confidentiality, integrity, and availability 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
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Subscriber Privilege Escalation in Estatik <= 4.3.5 versions.

Executive ViewAI

Why It Matters

The Estatik WordPress plugin (versions through 4.3.5) contains a critical privilege-escalation flaw that allows a Subscriber-level account to raise its own role, opening a path to full compromise of the affected website. Real-estate and listing sites are the primary exposure, because they frequently leave open user registration enabled, making the required low-privilege account trivial to obtain; the vendor-published CVSS 3.1 vector scores 9.8 under PR:N, while independent assessment indicates a Subscriber account (authenticated) is required. No public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, so leadership should treat every unpatched Estatik deployment as a live risk to site integrity, customer data, and brand trust.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable open user registration and restrict Subscriber account creation; remove or deactivate the Estatik plugin (versions through 4.3.5) if it is not essential; enforce least-privilege roles and multi-factor authentication for administrators; monitor and alert on privilege/role changes; apply WAF virtual patching for the plugin endpoint and run file-integrity checks on the WordPress installation.

Threat Intelligence Overview

EPSS Score
0.5%
Top 61% exploitable
Prevalence
Medium
Established WordPress real-estate listing plugin, common but industry-specific footprint
Data Quality
3 sources
Confidence: Low

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
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