Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as high-privilege WP user
-
DeliveryReach vulnerable Elementor editor endpoint
-
ExploitInject SQL via unsanitized parameter
-
ExecutionDatabase executes attacker query
-
ImpactExfiltrate sensitive database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress session with a high-privilege role (PR:H - typically Editor/Administrator level) that can access the Elementor editor functionality exposed by SKT Addons for Elementor version 4.0 or earlier; the plugin must be installed and active. No user interaction (UI:N) and no non-default configuration beyond having the plugin enabled are needed. The high-privilege requirement is the primary limiting factor: exploitation is not available to unauthenticated visitors or low-privilege subscribers, confining risk to insider misuse or a chained privilege compromise. |
| Impact | The vendor CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L, base 7.6) describes a network-reachable, low-complexity SQL injection that nonetheless requires high privileges (PR:H) - consistent with Patchstack's convention that an authenticated Editor/Admin-level WordPress account is needed to reach the vulnerable Elementor editor endpoint. This authentication gate is the single largest risk-reducer: an attacker must already hold a trusted, high-privilege role, which sharply limits the realistic threat population versus an unauthenticated SQLi. No EPSS score, no CISA KEV listing, and no public POC are present in the supplied intelligence, so exploitation status is 'no public exploit identified at time of analysis' - there is no evidence of active or automated exploitation. The impact profile is also unusual for a SQLi: the vendor set C:H but I:N and only A:L, implying primarily unauthorized data read (and a scope change, S:C, reflecting access to the backing database beyond the plugin's own security authority) rather than data tampering. Net: this is a moderately-severe, authenticated data-disclosure issue in a niche plugin, not a high-urgency internet-wide threat. Note the metric tension - a genuine SQL injection normally permits at least some write/integrity impact, so the vendor's I:N is conservative and worth verifying against the Patchstack advisory. |
| Exploit ScenarioDerived | An attacker who already holds a high-privilege WordPress account (e.g., a compromised or malicious Editor/Admin) submits crafted input to an Elementor editor endpoint provided by SKT Addons for Elementor <= 4.0, injecting SQL that the plugin passes unsanitized into a database query. This lets them read arbitrary database contents such as other users' data, password hashes, and secrets. No public exploit code is identified in the provided data, and the network vector with low complexity means exploitation is straightforward once the required privileged session is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 17, 2026
SQL injection in the SKT Addons for Elementor WordPress plugin (version 4.0 and earlier) allows an attacker who already holds a high-privilege authenticated WordPress account - PR:H in the vector, typically an Editor or Administrator able to reach the plugin's Elementor editor functionality - to inject arbitrary SQL against the site's backend database over the network with low attack complexity and no user interaction. The vendor-assigned CVSS 3.1 base score is 7.6 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L), while our independent assessment rates the same vector at AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N, i.e. confidentiality-heavy database disclosure rather than a scope-changing, integrity-destroying primitive. Because exploitation is gated behind the PR:H requirement, risk is concentrated in insider misuse or in an attacker who has already chained a separate privilege compromise; no public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV) for this CVE.
RemediationAI
No vendor-released patch was identified in the available intelligence at time of analysis, and no fixed version number is published in the CVE, CPE or EUVD records, so the first action is to monitor the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/skt-addons-for-elementor/vulnerability/wordpress-skt-addons-for-elementor-plugin-4-0-sql-injection-vulnerability?_s_id=cve) for the patched release and apply it as soon as it appears; do not assume that version 4.0 is the final affected build. As compensating controls, deactivate and, if feasible, remove the SKT Addons for Elementor plugin on sites that do not actively use its Elementor widgets - the trade-off is loss of the custom widgets and any layouts that embed them. If the plugin must stay enabled, strictly minimize the population of high-privilege accounts (Administrator and Editor) that can reach the Elementor editor, apply least privilege and role auditing to those accounts, and enforce strong authentication/MFA plus session review on them, since PR:H is the primary limiting factor - this reduces but does not eliminate insider risk. Deploy a web application firewall or database-layer rule set tuned to reject SQL metacharacters and UNION/stacked-query patterns on editor-scoped plugin requests, and enable database query logging or a WordPress security plugin with SQLi heuristics to detect probing; both add latency and potential false positives on legitimate editor traffic. Finally, rotate database credentials and review exposure of sensitive options and password hashes if any suspicious editor-scoped requests are observed, and treat the confidentiality-heavy impact (C:H with bounded integrity) as the reason to prioritize data-leak containment over availability work.
Affected VersionsENISA
Affected Packages
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 flaw is a classic CWE-89 SQL injection in a WordPress plugin, SKT Addons for Elementor, which extends the Elementor page builder with additional widgets and editor-side functionality. The CPE cpe:2.3:a:sonal_s_sinha:skt_addons_for_elementor:*:*:*:*:*:*:*:* identifies the affected distribution (vendor mapping 'sonal_s_sinha') and the EUVD record EUVD-2026-81508 lists all versions up to and including 4.0 as vulnerable. The vulnerable path is reached through the plugin's editor-facing request handling, where user-supplied parameters are incorporated into a database query without adequate parameterization or escaping; because the affected endpoint is registered in the editor context, an authenticated session with a sufficiently privileged WordPress role is required to reach it, which is exactly what the PR:H metric in both the vendor and independent vectors reflects. The practical consequence of a successful injection is read access to WordPress tables (users, options, and plugin-specific tables), which can expose password hashes, salts, API keys and other secrets; write capability is bounded (the vendor vector scores I:N, our assessment I:L), so the dominant impact class is confidential data disclosure rather than full site takeover. The disagreement between the vendor and independent scoring on scope (S:C vs S:U) and integrity/availability (I:N/A:L vs I:L/A:N) should be treated as an indicator that the exact reachable query and its side effects were not fully enumerated by either party.
Know when Skt Addons For Elementor 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
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
Network-reachable, low-complexity SQLi gated behind a high-privilege WP account (PR:H); SQL injection realistically permits at least minor data modification (I:L) alongside high read impact, and I keep scope unchanged (S:U).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Editor SQL Injection in SKT Addons for Elementor <= 4.0 versions.
Executive ViewAI
A high-severity SQL injection flaw in the SKT Addons for Elementor WordPress plugin (version 4.0 and earlier) could let someone who already holds an Editor or Administrator account read sensitive data directly out of the website's backend database. Because the flaw requires high-privilege credentials rather than anonymous access, the practical exposure is limited to insider misuse or an attacker who has already breached an account through a separate compromise; no vendor patch is currently available, leaving plugin removal or access restriction as the only reliable near-term answer. Leadership should care because any WordPress site running this plugin with broadly delegated Editor rights effectively has an unpatchable, credentialed database disclosure path sitting in production.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the SKT Addons for Elementor plugin (version 4.0 and earlier) where feasible; restrict and audit Editor/Administrator accounts to reduce the set of users who can reach the vulnerable Elementor editor functionality; enforce least privilege and multi-factor authentication on high-privilege WordPress accounts; deploy web application firewall or database monitoring rules to detect anomalous SQL activity; and maintain current, tested database backups to limit disclosure impact.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Skt Addons For Elementor
View allThe SKT Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Age Gate
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SKT Themes SKT Add
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SKT Themes SKT Add
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in SKT Themes
The SKT Addons for Elementor plugin for WordPress is vulnerable to Information Exposure in all versions up to, and inclu
EUVD-2026-81508
GHSA-prg3-74hq-mg2x
NVD
CVE.org
EPSS
Exploit-DB