Skip to main content

Live Copy Paste CVE-2026-93527

| EUVDEUVD-2026-85460 HIGH
SQL Injection (CWE-89)
2026-09-23 Patchstack GHSA-phgv-fx62-f937
8.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Obtain Contributor account on WordPress site
  2. Delivery
    Send crafted request to plugin endpoint
  3. Exploit
    Inject SQL via unsanitized parameter
  4. Execution
    Query executes against WordPress database
  5. Impact
    Exfiltrate user data and password hashes

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 account with at least Contributor role (PR:L) on a site running bdthemes Live Copy Paste for Elementor plugin version 1.5.10 or earlier, with Elementor installed. No user interaction is required (UI:N) and the vulnerable endpoint is network-reachable. Limiting factors: the attacker must possess or obtain valid Contributor credentials, so sites that do not allow Contributor-level registration or multi-author access substantially reduce real-world exposure; exploitation is not possible unauthenticated. No non-default plugin configuration is indicated by the available data beyond the plugin simply being installed and active.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L, base 8.5) describes a network-reachable, low-complexity SQL injection requiring only Contributor-level authentication (PR:L). The impact profile is confidentiality-weighted (C:H) with limited availability impact (A:L) and no integrity impact (I:N), consistent with a read-oriented SQLi that lets a low-privileged user extract arbitrary database contents (WordPress users, password hashes, secrets). The S:C (scope change) reflects the injected query reaching the shared database beyond the plugin's own security authority - a scoring convention Patchstack commonly applies, though a stricter reading would treat same-database SQLi as S:U (which would lower the base score). No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the 8.5 is a capability rating, not an exploitation-in-the-wild signal. The realistic priority is moderate: the flaw is genuinely exploitable but gated behind having a valid Contributor account on the target WordPress site, which meaningfully narrows the attacker population versus an unauthenticated bug. On a site that hands out Contributor accounts (multi-author blogs, membership sites), this is a serious privilege-to-data-breach path; on a single-admin site it is largely inert.

Exploit ScenarioDerived

An attacker who holds (or registers/phishes) a Contributor account on a WordPress site running Live Copy Paste for Elementor <= 1.5.10 submits a crafted request to the vulnerable plugin endpoint, embedding SQL into an insufficiently sanitized parameter. The injected query executes against the WordPress database, letting the attacker dump sensitive data such as user records and password hashes, escalating from a low-privilege author to full data compromise. No public POC was provided, and exploitation requires an authenticated Contributor session (PR:L), so it cannot be launched fully anonymously.

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 – Sep 23, 2026

SQL injection in the Live Copy Paste for Elementor WordPress plugin (bdthemes, versions up to and including 1.5.10) allows an authenticated attacker holding at least Contributor-level credentials to inject arbitrary SQL through a network-reachable plugin endpoint, resulting in high-impact confidentiality exposure (database contents, including user and configuration data) and a limited availability effect. No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); EPSS data was not provided. The vendor-published vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L, 8.5) is treated in our independent assessment as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L, with the same base 8.5 and the same Contributor-authentication prerequisite, so real-world exposure is concentrated on multi-author sites that permit Contributor registration or low-privileged content workflows.

RemediationAI

No vendor-released patch version is identified in the available data, so operators should first verify the current release status of the Live Copy Paste for Elementor plugin on its WordPress.org plugin page and the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/live-copy-paste/vulnerability/wordpress-live-copy-paste-for-elementor-plugin-1-5-10-sql-injection-vulnerability?_s_id=cve) and upgrade to the first version published after 1.5.10 as soon as it becomes available. Where no fix is yet deployable, the single most effective compensating control is to remove or deactivate the plugin (trade-off: loss of its copy/paste functionality inside Elementor, which may disrupt editorial workflows) - that eliminates the vulnerable endpoint entirely. If the plugin must remain active, tighten the authentication prerequisite the vulnerability depends on: disable open user registration and set the default new-user role above Contributor, and audit existing accounts to remove unnecessary Contributor-level users (trade-off: it constrains legitimate multi-author publishing and onboarding). Also restrict access to plugin entry points at the web tier (WAF rule or reverse-proxy rule blocking the plugin's AJAX/REST routes to unauthenticated or low-privileged sessions) and, where feasible, limit wp-admin and admin-ajax.php access by IP allow-list (trade-off: can break legitimate remote editors and mobile access). Because the impact is database read rather than write, rotate database-exposed secrets (WordPress salts, API keys stored in options) if an intrusion is suspected, and monitor for anomalous SQL errors or bulk option/user-table reads in the interim.

Affected VersionsENISA

Live Copy Paste for Elementor n/a ≤1.5.10

Affected Packages

euvd live_copy_paste_for_elementor 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 vulnerable component is a WordPress plugin that extends the Elementor page builder with copy/paste functionality for page layouts. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), meaning attacker-supplied input reaches a database query without adequate parameterization or escaping - typically a plugin REST/AJAX handler or admin-post action that concatenates a request parameter directly into a SELECT/SQL statement rather than using WordPress's $wpdb->prepare(). Because the endpoint is exposed through WordPress's normal HTTP surface, exploitation is remote (AV:N) and needs no user interaction (UI:N), but the CVSS vector shows PR:L, so the attacker must first hold a valid Contributor account; the CPE entry cpe:2.3:a:bdthemes:live_copy_paste_for_elementor:*:*:*:*:*:*:*:* indicates the affected product is tracked as an unbounded version range (all released versions through 1.5.10), and the plugin requires Elementor to be installed for its functionality to be reachable. The source advisory lists S:C (scope change) while our assessment uses S:U; impact on confidentiality (C:H) and limited availability (A:L) is consistent across both, and no integrity impact is claimed. The vulnerability was reported through the Patchstack vulnerability database.

Know when Live Copy Paste 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

Vendor (Patchstack) PRIMARY 8.5 HIGH
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 7.1 HIGH

Network SQLi needing only a Contributor account gives AV:N/AC:L/PR:L/UI:N; same-database injection is scored S:U (vs vendor S:C), with C:H read exposure and A:L, no integrity impact.

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

DescriptionCVE.org

Contributor SQL Injection in Live Copy Paste for Elementor <= 1.5.10 versions.

Executive ViewAI

Why It Matters

A high-severity SQL injection flaw in the Live Copy Paste for Elementor WordPress plugin (bdthemes, versions up to and including 1.5.10) lets any user with Contributor-level access read the site's underlying database, including user records and configuration data. Because the plugin is widely deployed on multi-author and community-contributed WordPress sites, leadership should treat every site that allows Contributor registration or low-privilege content workflows as an exposed data-breach surface, and no vendor patch is currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the plugin on all sites running version 1.5.10 or earlier; block Contributor-level registration and revoke untrusted Contributor accounts; deploy WAF rules targeting SQL injection against plugin endpoints; audit and rotate database-stored credentials and secrets; monitor for anomalous database access.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Low
niche bdthemes Elementor add-on plugin, not core WordPress or Elementor itself
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 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
No
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

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