Security readout for executives and security teams
Plain-English summary
CVE-2026-1206 lets a logged-in WordPress user with Contributor-level access or higher read private or draft Elementor template content. It is not a full site takeover issue, but it can expose unpublished page designs or sensitive content stored in templates. Public sources rate it medium severity.
Executive priority
Treat as a near-term maintenance and access-control issue, not an emergency unless many non-employee Contributor accounts exist. Prioritize public or partner-managed WordPress sites and sites where draft templates may contain confidential content.
Technical view
Elementor Website Builder for WordPress versions up to and including 3.35.7 has an incorrect authorization flaw in is_allowed_to_read_template(). Non-published templates can be treated as readable without verifying edit capability. An authenticated Contributor+ user can request template data through the elementor_ajax get_template_data action using a template_id.
Likely exposure
Exposure is mainly WordPress sites using Elementor up to 3.35.7 where untrusted or semi-trusted users have Contributor or higher accounts. Sites without such users have lower practical exposure, based on the published privilege requirement.
Exploitation context
The CVE requires network access and a valid authenticated WordPress account with Contributor-level privileges or above. Public sources provided do not indicate active exploitation, and the CVE is not listed as KEV in the supplied data.
Researcher notes
The issue maps to CWE-639 and CVSS 4.3, reflecting authenticated, low-privilege, confidentiality-only impact. The supplied WordPress Trac changeset is relevant patch evidence, but public sources here do not provide exploitation-in-the-wild evidence.
Mitigation direction
- Update Elementor to a version newer than 3.35.7 when available from the vendor.
- Review Elementor and WordPress.org plugin guidance for the patched release details.
- Limit Contributor and higher accounts to trusted users only.
- Remove stale WordPress accounts that no longer need access.
- Avoid storing secrets or sensitive business data inside draft/private templates.
Validation and detection
- Inventory WordPress sites using the Elementor Website Builder plugin.
- Check installed Elementor versions and flag versions 3.35.7 or earlier.
- Review whether Contributor or higher accounts exist on affected sites.
- Confirm vendor patch adoption through plugin changelog or WordPress admin.
- Audit sensitive draft/private Elementor templates for exposed content risk.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1206 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/a4420935-4952-4460-afc2-1c6df6965b3d?source=cveCVE reference
- https://plugins.trac.wordpress.org/changeset/3489160/elementor/trunk/includes/template-library/sources/local.php?old=3473768&old_path=elementor%2Ftrunk%2Fincludes%2Ftemplate-library%2Fsources%2Flocal.phpCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.