CVE-2026-47227

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
6.5EG
EchelonGraph verdictPlan a fixRemediate 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.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Admidio is an open-source user management solution. modules/categories.php checks that the supplied type parameter (ANN, EVT, ROL, USF, …) corresponds to a module the actor administers. The follow-up "is this specific category editable by me" check at lines 56-61 is dead code because it compares $getType (a category-type code) against mode names (edit/save/delete); the condition is permanently false, so $category->isEditable() is never invoked. Prior to version 5.0.10, the delete, sequence, and save switch cases load the category by the supplied UUID and act on it without re-checking that the category belongs to a module the actor administers. A user holding only one module-administrator right can therefore destroy or reorder empty categories belonging to *other* modules — for example, an announcements administrator can delete role categories, profile-field categories, or weblink categories that they have no right to touch. Version 5.0.10 fixes the issue.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% 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).

A fix is available. Apply it within your standard update timelines.

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

May 29, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Module-administrator can delete or reorder categories owned by other modules via dead authorization check in `modules/categories.php` · Advisory · Admidio/admidio · GitHub

https://github.com/Admidio/admidio/security/advisories/GHSA-rwjr-qjj3-mq2f

Vendor Advisories for CVE-2026-47227(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
admidio/admidio4.1.0 ... v5.0.9 (55 versions)
  • every version up to 5.0.10: fixed in 5.0.10
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-18 03:36 UTCEG score recompute
  4. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-12 16:02 UTCEG score recompute
  11. 2026-10-11 19:44 UTCEG score recompute
  12. 2026-10-11 16:59 UTCEG score recompute
  13. 2026-10-11 14:24 UTCEG score recompute
  14. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-10-03 14:48 UTCOSV refresh
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
Show 55 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-09-14 06:22 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-09-09 23:00 UTCEG score recompute
  17. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  18. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  26. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  27. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  28. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-08-25 04:15 UTCEG score recompute
  30. 2026-08-23 14:10 UTCEG score recompute
  31. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-08-21 14:59 UTCEG score recompute
  34. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-08-20 10:24 UTCEG score recompute
  36. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  38. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-08-17 06:51 UTCEG score recompute
  40. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-08-16 02:24 UTCEG score recompute
  42. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-08-14 00:27 UTCEG score recompute
  45. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-08-12 16:36 UTCEG score recompute
  47. 2026-08-12 15:37 UTCEG score recompute
  48. 2026-08-12 14:27 UTCEG score recompute
  49. 2026-07-31 05:51 UTCEG score recompute
  50. 2026-07-27 03:13 UTCEG score recompute
  51. 2026-07-23 03:17 UTCEG score recompute
  52. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 8th percentile
  53. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 8th percentile
  54. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · 8th percentile
  55. 2026-05-29 22:26 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-47227?
CVE-2026-47227 is a medium-severity vulnerability; its CVE record was published on May 29, 2026. Admidio is an open-source user management solution. modules/categories.php checks that the supplied type parameter (ANN, EVT, ROL, USF, …) corresponds to a module the actor administers. The follow-up "is this specific category editable by me" check at lines 56-61 is dead code because it compares…
When was the CVE record for CVE-2026-47227 published?
The CVE record for CVE-2026-47227 was published on May 29, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-47227 actively exploited?
CVE-2026-47227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47227?
CVE-2026-47227 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47227?
A fix for CVE-2026-47227 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47227 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47227

Explore →

Is Your Infrastructure Affected by CVE-2026-47227?

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

Book a Demo →Browse All CVEs