The Insert Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via post custom field keys (meta key names) in all versions up to, and including, 3.11.4. This is due to insufficient output escaping in the the_meta() function: while the custom field VALUE is sanitized with wp_kses_post(), the custom field KEY ($key) is interpolated into the rendered HTML (lines 1786-1791) and echoed (line 1806) without any escaping when an inserted page is rendered with the [insert page='ID' display='all'] shortcode. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVE-2026-10089
Score 6.4 from GitHub Security Advisory published 2026-07-02. a secondary CVSS source baseline 6.4; sources differ by 0.0.
- 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
- 6.4
- EG Score
- 6.4(high)
- EPSS
- 12.2%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
July 2, 2026
References (8)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/insert-pages/tags/3.11.3/insert-pages.php#L1771
- security@wordfencehttps://plugins.trac.wordpress.org/browser/insert-pages/tags/3.11.3/insert-pages.php#L1789
- security@wordfencehttps://plugins.trac.wordpress.org/browser/insert-pages/tags/3.11.3/insert-pages.php#L768
- security@wordfencehttps://plugins.trac.wordpress.org/browser/insert-pages/tags/3.11.4/insert-pages.php#L1771
- security@wordfencehttps://plugins.trac.wordpress.org/browser/insert-pages/tags/3.11.4/insert-pages.php#L1789
- security@wordfencehttps://plugins.trac.wordpress.org/browser/insert-pages/tags/3.11.4/insert-pages.php#L768
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3579298
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/a4246181-d331-46b0-ad48-e2ece11b2f5f?source=cve
Vendor Advisories for CVE-2026-10089(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 17× in last 7d / 17× 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-07-07 03:53 UTCEG score recompute
- 2026-07-07 03:52 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 04:32 UTCEG score recompute
- 2026-07-06 04:31 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 05:15 UTCEG score recompute
- 2026-07-05 05:14 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 05:55 UTCEG score recompute
- 2026-07-04 05:55 UTCGHSA enrichment
- 2026-07-03 06:38 UTCEG score recompute
- 2026-07-03 06:38 UTCGHSA enrichment
- 2026-07-02 07:18 UTCEG score recompute
- 2026-07-02 07:18 UTCGHSA enrichment
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-10089?
When was CVE-2026-10089 disclosed?
Is CVE-2026-10089 actively exploited?
What is the CVSS score of CVE-2026-10089?
How do I remediate CVE-2026-10089?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-10089
Is Your Infrastructure Affected by CVE-2026-10089?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.