CVE-2026-12094

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.3 from GitHub Security Advisory published 2026-06-24. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-38663 (ENISA EUVD) · GHSA-7v85-67q3-8qc9 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Wordfence) lists iamranit Advanced Contact Form 7 – Compact DB versions up to and including 1.0.0 as affected. No release containing a fix is confirmed on record.

The Advanced Contact Form 7 - Compact DB plugin for WordPress is vulnerable to unauthorized deletion of data due to a missing capability check on the cf7cdb_ajax_delete_user() function in versions up to, and including, 1.0.0. The handler is registered against both wp_ajax_cf7cdb_delete and wp_ajax_nopriv_cf7cdb_delete, and it performs no nonce verification, no capability check, and no ownership check before invoking $wpdb->delete() against the wp_cf7cdb_data table with an attacker-supplied integer ID. This makes it possible for unauthenticated attackers to delete arbitrary contact form submission entries stored by the plugin by iterating sequential primary-key IDs.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 24, 2026

Last Modified

June 25, 2026

Vendor Advisories for CVE-2026-12094(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 10× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 204 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-25 14:50 UTCEG score recompute
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-23 07:36 UTCEG score recompute
  8. 2026-10-23 07:36 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  9. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-18 05:04 UTCEG score recompute
  15. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-12 16:36 UTCEG score recompute
  21. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-11 20:12 UTCEG score recompute
  23. 2026-10-11 18:24 UTCEG score recompute
  24. 2026-10-11 14:58 UTCEG score recompute
  25. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 75 more
  1. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-09-23 11:56 UTCEG score recompute
  16. 2026-09-23 11:56 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  17. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-09-18 10:17 UTCEG score recompute
  20. 2026-09-18 10:17 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  21. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-09-13 12:17 UTCEG score recompute
  24. 2026-09-13 12:17 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  25. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  27. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  33. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  36. 2026-08-30 20:23 UTCEG score recompute
  37. 2026-08-30 20:23 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  38. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  39. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  41. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-08-24 22:04 UTCEG score recompute
  44. 2026-08-24 22:04 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  45. 2026-08-23 15:18 UTCEG score recompute
  46. 2026-08-23 15:18 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  47. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  48. 2026-08-22 13:41 UTCEG score recompute
  49. 2026-08-22 13:41 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  50. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-08-21 09:24 UTCEG score recompute
  52. 2026-08-21 09:24 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  53. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-08-20 07:44 UTCEG score recompute
  55. 2026-08-20 07:44 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  56. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  57. 2026-08-19 04:47 UTCEG score recompute
  58. 2026-08-19 04:47 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  59. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  60. 2026-08-17 11:57 UTCEG score recompute
  61. 2026-08-17 11:57 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  62. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  63. 2026-08-16 10:20 UTCEG score recompute
  64. 2026-08-16 10:20 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  65. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  66. 2026-08-15 08:44 UTCEG score recompute
  67. 2026-08-15 08:44 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  68. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  69. 2026-08-14 06:20 UTCEG score recompute
  70. 2026-08-14 06:20 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  71. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  72. 2026-08-13 04:43 UTCEG score recompute
  73. 2026-08-13 04:43 UTCGHSA enrichmentGHSA-7v85-67q3-8qc9 · GitHub CVSS 5.3
  74. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  75. 2026-08-12 03:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-12094?
CVE-2026-12094 is a medium-severity vulnerability; its CVE record was published on June 24, 2026. The Advanced Contact Form 7 - Compact DB plugin for WordPress is vulnerable to unauthorized deletion of data due to a missing capability check on the cf7cdbajaxdeleteuser() function in versions up to, and including, 1.0.0. The handler is registered against both wpajaxcf7cdbdelete and…
When was the CVE record for CVE-2026-12094 published?
The CVE record for CVE-2026-12094 was published on June 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-12094 actively exploited?
CVE-2026-12094 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12094?
CVE-2026-12094 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12094?
No fix for CVE-2026-12094 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Wordfence) lists iamranit Advanced Contact Form 7 – Compact DB versions up to and including 1.0.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-12094 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12094?

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