The Royal Addons for Elementor WordPress plugin before 1.7.1066 does not perform any capability or ownership check (relying only on a publicly-scrapeable nonce) before writing like-count and visitor-tracking post meta keyed on an arbitrary post ID, allowing unauthenticated users to modify that metadata on any post, including private and draft posts.
CVE-2026-13404
This medium-severity CVE scores 5.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 26, 2026Royal Elementor Addons < 1.7.1066 – Unauthenticated Like Count and IP Meta Modification via wpr_likes_init | CVE 2026-13404 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/c4915a6c-8bf5-46aa-8134-ea490bd6137f/Vendor Advisories for CVE-2026-13404(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 15:04 UTCEG score recompute▲ 5.30
- 2026-08-26 15:01 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
- 2026-08-26 06:10 UTCEG score recompute
- 2026-08-26 06:08 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-13404?
When was CVE-2026-13404 disclosed?
Is CVE-2026-13404 actively exploited?
What is the CVSS score of CVE-2026-13404?
How do I remediate CVE-2026-13404?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13404
Is Your Infrastructure Affected by CVE-2026-13404?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.