- Exploited
- No known exploitation
- Fix
- Fixed in 1.3.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.3.1.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Dynific Addons for Elementor (formerly Anywhere Elementor) WordPress plugin does not check post status or user permissions when it resolves post IDs in one of its shortcodes. A logged-in user with Contributor role or higher can therefore view the content of other users' draft, private, and password-protected posts, and an Author can republish that content to anonymous visitors.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Dynific Addons for Elementor (formerly Anywhere Elementor) WordPress plugin before 1.3.1 does not perform a status or capability check when resolving post identifiers passed to one of its shortcodes, allowing authenticated users with at least the Contributor role to disclose the content of other users' draft, private and password-protected posts. An Author can republish that content to anonymous visitors.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.3.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-117524 (Dynific Addons for Elementor 1.3 - Contributor+ Arbitrary Post Content Disclosure via dynific_template Shortcode), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-117524 (entry last updated 2026-11-11): Affected: - Unknown Dynific Addons for Elementor (formerly Anywhere Elementor): from 1.3.0, fixed in 1.3.1 Fixed versions: 1.3.1. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-117524 is not listed as of cve.now's last read. This KEV status is for CVE-2026-117524 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - the references on https://cve.now/CVE-2026-117524 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-117524 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-117524.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Unknown Dynific Addons for Elementor (formerly Anywhere Elementor)
From 1.3.0 · fixed in 1.3.1
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-117524
Is CVE-2026-117524 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-117524?
Dynific Addons for Elementor (formerly Anywhere Elementor): from 1.3.0 before 1.3.1.Source: cve.now feed data
How do I fix CVE-2026-117524?
Upgrade to a fixed version: 1.3.1.Source: cve.now feed data