CVE-2025-69122

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-17. A secondary CVSS source baseline 9.8; 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
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

Unauthenticated PHP Object Injection in SeaFood Company <= 1.4 versions.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* 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, and watch the vendor's advisory for the fix.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 17, 2026

Last Modified

October 6, 2026

Advisory Details (1)

Auto-updated Oct 6, 2026
No fix on record yet.
Web pageMentions a patch (unverified)

PHP Object Injection in WordPress SeaFood Company Theme - Patchstack

https://patchstack.com/database/wordpress/theme/seafood-company/vulnerability/wordpress-seafood-company-theme-1-4-php-object-injection-vulnerability?_s_id=cve

Vendor Advisories for CVE-2025-69122(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 14× in last 7d / 36× 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 99 of 460 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 361 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-69122?
CVE-2025-69122 is a critical-severity vulnerability; its CVE record was published on June 17, 2026. Unauthenticated PHP Object Injection in SeaFood Company <= 1.4 versions.
When was the CVE record for CVE-2025-69122 published?
The CVE record for CVE-2025-69122 was published on June 17, 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 October 6, 2026; the record at its source may have been updated since.
Is CVE-2025-69122 actively exploited?
CVE-2025-69122 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-69122?
CVE-2025-69122 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-69122?
No fix for CVE-2025-69122 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 vendor advisories EchelonGraph has for CVE-2025-69122 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-69122

Explore →

Is Your Infrastructure Affected by CVE-2025-69122?

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

Book a Demo →Browse All CVEs