CVE-2026-10096

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-01. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Qi Blocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.4.9 via the 'page_id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with author-level access and above, to modify the stored Qi Blocks styles of arbitrary posts, templates, or widgets they do not own — including site-wide surfaces via the reserved 'template' and 'widget' page_id values — enabling unauthorized frontend defacement, content hiding, and degradation of any page on the site. The endpoint's permission_callback checks only the generic edit_posts and publish_posts capabilities, meaning any user with the built-in Author role satisfies the check regardless of post ownership.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
24(Track)
EG Risk 24/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 computed
Severity43% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
9.6%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 1, 2026

References (5)

Vendor Advisories for CVE-2026-10096(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 8× in last 7d / 45× 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.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:04 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 02:04 UTCGHSA enrichment
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-16 03:48 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 05:39 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 07:29 UTCGHSA enrichment
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 09:19 UTCGHSA enrichment
  18. 2026-07-13 06:12 UTCEPSS rescore
  19. 2026-07-12 11:11 UTCGHSA enrichment
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-11 13:02 UTCGHSA enrichment
  22. 2026-07-11 08:27 UTCEPSS rescore
  23. 2026-07-10 14:53 UTCGHSA enrichment
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 16:44 UTCGHSA enrichment
Show 20 more
  1. 2026-07-08 18:34 UTCGHSA enrichment
  2. 2026-07-08 15:15 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 20:25 UTCGHSA enrichment
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 22:17 UTCGHSA enrichment
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:07 UTCGHSA enrichment
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-05 01:58 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 03:50 UTCGHSA enrichment
  15. 2026-07-03 05:41 UTCGHSA enrichment
  16. 2026-07-02 07:32 UTCGHSA enrichment
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 09:23 UTCEG score recompute
  20. 2026-07-01 09:22 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-10096?
CVE-2026-10096 is a medium vulnerability published on July 1, 2026. The Qi Blocks plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.4.9 via the 'pageid' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with author-level access and above, to…
When was CVE-2026-10096 disclosed?
CVE-2026-10096 was first published in the National Vulnerability Database on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10096 actively exploited?
CVE-2026-10096 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10096?
CVE-2026-10096 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-10096?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10096, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10096

Explore →

Is Your Infrastructure Affected by CVE-2026-10096?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs