CVE-2026-57859

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:vulncheck, epss
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

e107 prior to version 2.3.8 contains a code execution vulnerability in the e_array deserialization handler that allows an attacker with out-of-band database write access to execute arbitrary PHP code by storing a crafted payload in the user_prefs column. The e_array::unserialize() function in e107_handlers/core_functions.php performs only a prefix check for the string 'array' before passing the stored value to eval(), causing automatic PHP execution whenever the affected user's preferences are materialized through e_user_pref::load().

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track*)
EG Risk 50/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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 14, 2026

Advisory Details (4)

Auto-updated Jul 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic

e107 Second-Order Code Execution via eval()-Based Deserialization in e_array::unserialize() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/e107-second-order-code-execution-via-eval-based-deserialization-in-e-array-unserialize
generic

GitHub - e107inc/e107: e107 Bootstrap CMS (Content Management System) v2 with PHP, MySQL, HTML5, jQuery and Twitter Bootstrap. Issue Discussion Room: https://gitter.im/e107inc/e107 · GitHub

https://github.com/e107inc/e107
github_commit

commit 40e73cefde85 (e107inc/e107)

Fix landed in e107inc/e107 commit 40e73cefde85 — awaiting tagged release

https://github.com/e107inc/e107/commit/40e73cefde85b32e1227dfac9956a5cb87046277
github Patch Available🟡 PoC Available

Second-order code execution via eval()-based deserialization in e107::unserialize() · Advisory · e107inc/e107 · GitHub

https://github.com/e107inc/e107/security/advisories/GHSA-568x-w5qj-vr7c

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 56× 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-08-28 21:42 UTCEPSS rescore
  2. 2026-08-27 21:16 UTCEG score recompute
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 19:19 UTCEG score recompute
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 14:44 UTCEG score recompute
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-25 02:21 UTCEG score recompute
  9. 2026-08-24 13:58 UTCEG score recompute
  10. 2026-08-23 00:36 UTCEG score recompute
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-21 23:50 UTCEG score recompute
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 11:27 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 21:56 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 21:07 UTCEG score recompute
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 19:48 UTCEG score recompute
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 18:50 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 06:20 UTCEG score recompute
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 31 more
  1. 2026-08-15 05:35 UTCEG score recompute
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 10:19 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 21:10 UTCEG score recompute
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-11 20:21 UTCEG score recompute
  8. 2026-08-11 07:58 UTCEG score recompute
  9. 2026-08-11 00:00 UTCEPSS rescore
  10. 2026-08-09 18:50 UTCEG score recompute
  11. 2026-08-09 13:46 UTCEPSS rescore
  12. 2026-08-08 18:06 UTCEG score recompute
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-07 17:21 UTCEG score recompute
  15. 2026-08-06 16:35 UTCEG score recompute
  16. 2026-08-06 13:47 UTCEPSS rescore
  17. 2026-08-06 04:11 UTCEG score recompute
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-05 03:25 UTCEG score recompute
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 15:03 UTCEG score recompute
  22. 2026-08-04 10:39 UTCEPSS rescore
  23. 2026-08-03 14:18 UTCEG score recompute
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-01 12:47 UTCEG score recompute
  26. 2026-08-01 04:16 UTCEPSS rescore
  27. 2026-07-31 12:00 UTCEG score recompute
  28. 2026-07-30 15:32 UTCEG score recompute
  29. 2026-07-30 14:29 UTCEG score recompute
  30. 2026-07-30 14:06 UTCEG score recompute
  31. 2026-07-30 14:06 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57859?
CVE-2026-57859 is a high vulnerability published on July 30, 2026. e107 prior to version 2.3.8 contains a code execution vulnerability in the earray deserialization handler that allows an attacker with out-of-band database write access to execute arbitrary PHP code by storing a crafted payload in the userprefs column. The earray::unserialize() function in…
When was CVE-2026-57859 disclosed?
CVE-2026-57859 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57859 actively exploited?
CVE-2026-57859 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.2% of all scored CVEs.
What is the CVSS score of CVE-2026-57859?
CVE-2026-57859 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-57859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57859, 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-57859

Explore →

Is Your Infrastructure Affected by CVE-2026-57859?

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

Start Free Scan →Browse All CVEs