The Static Block plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.2. This is due to the static_block_content() shortcode handler retrieving a post via get_post() using an attacker-supplied 'id' attribute and outputting its post_content without verifying the post's status (private, draft, pending) or the requesting user's capability to view it. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary posts, including private and draft static blocks (and any other post type) created by administrators, by embedding the [static_block_content id="X"] shortcode in their own content and previewing it.
CVE-2026-10780
Score 4.3 from GitHub Security Advisory published 2026-06-16. a secondary CVSS source baseline 4.3; 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
- 4.3
- EG Score
- 4.3(high)
- EPSS
- 11.4%
- KEV
- Not listed
Published
June 16, 2026
Last Modified
June 16, 2026
References (4)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/static-block/trunk/static-block.php#L244
- security@wordfencehttps://plugins.trac.wordpress.org/browser/static-block/trunk/static-block.php#L268
- security@wordfencehttps://plugins.trac.wordpress.org/browser/static-block/trunk/static-block.php#L270
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/f88c00ca-cf9e-44e7-9495-686ace1ead21?source=cve
Vendor Advisories for CVE-2026-10780(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 20× in last 7d / 66× 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-06 23:28 UTCEG score recompute
- 2026-07-06 23:28 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 10:47 UTCEG score recompute
- 2026-07-05 10:47 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 09:26 UTCEG score recompute
- 2026-07-04 09:25 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 07:24 UTCEG score recompute
- 2026-07-03 07:24 UTCGHSA enrichment
- 2026-07-02 06:04 UTCEG score recompute
- 2026-07-02 06:04 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 04:42 UTCEG score recompute
- 2026-07-01 04:42 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 03:09 UTCEG score recompute
- 2026-06-30 03:09 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 01:48 UTCEG score recompute
- 2026-06-29 01:48 UTCGHSA enrichment
Show 41 moreShow fewer
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 00:27 UTCEG score recompute
- 2026-06-28 00:27 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 22:52 UTCEG score recompute
- 2026-06-26 22:52 UTCGHSA enrichment
- 2026-06-25 21:23 UTCEG score recompute
- 2026-06-25 21:23 UTCGHSA enrichment
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 20:02 UTCEG score recompute
- 2026-06-24 20:01 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:32 UTCEPSS rescore
- 2026-06-23 16:46 UTCEG score recompute
- 2026-06-23 16:46 UTCGHSA enrichment
- 2026-06-22 15:23 UTCEG score recompute
- 2026-06-22 15:23 UTCGHSA enrichment
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 13:59 UTCEG score recompute
- 2026-06-21 13:59 UTCGHSA enrichment
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-20 12:27 UTCEG score recompute
- 2026-06-20 12:27 UTCGHSA enrichment
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-19 11:04 UTCEG score recompute
- 2026-06-19 11:04 UTCGHSA enrichment
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 09:35 UTCEG score recompute
- 2026-06-18 09:35 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 08:06 UTCEG score recompute
- 2026-06-17 08:05 UTCGHSA enrichment
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 06:44 UTCEG score recompute
- 2026-06-16 06:44 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-10780?
When was CVE-2026-10780 disclosed?
Is CVE-2026-10780 actively exploited?
What is the CVSS score of CVE-2026-10780?
How do I remediate CVE-2026-10780?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-10780
Is Your Infrastructure Affected by CVE-2026-10780?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.