CVE-2016-20054

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

Score 4.3 from GitHub Security Advisory published 2026-04-04. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
4.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

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

Nodcms contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized administrative actions by crafting malicious forms. Attackers can trick authenticated administrators into submitting requests to admin/user_manipulate and admin/settings/generall endpoints to create users or modify application settings without explicit consent.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/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)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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 within your standard update timelines, and watch for a fix.
EPSS PROB
0.1%
EPSS %ILE
1st
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 (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 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 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

April 4, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
No fix on record yet.
Web page

nodCMS - Cross-Site Request Forgery - PHP webapps Exploit

https://www.exploit-db.com/exploits/40707

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerkhodakhah/nodcms—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
khodakhah/nodcms3.2.0, 3.3.0
  • every version through 3.4.1: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 97 of 172 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Packagist:khodakhah/nodcms

Frequently asked(5)

What is CVE-2016-20054?
CVE-2016-20054 is a medium-severity vulnerability; its CVE record was published on April 4, 2026. Nodcms contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized administrative actions by crafting malicious forms. Attackers can trick authenticated administrators into submitting requests to admin/user_manipulate and admin/settings/generall endpoints to…
When was the CVE record for CVE-2016-20054 published?
The CVE record for CVE-2016-20054 was published on April 4, 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 8, 2026; the record at its source may have been updated since.
Is CVE-2016-20054 actively exploited?
CVE-2016-20054 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-20054?
CVE-2016-20054 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2016-20054?
No fix for CVE-2016-20054 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-20054

Explore →

Is Your Infrastructure Affected by CVE-2016-20054?

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

Book a Demo →Browse All CVEs