CVE-2022-22909

HIGHNVD 8.88.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 45% probability of exploitation within the next 30 days (top 1.3% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 45%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

HotelDruid v3.0.3 was discovered to contain a remote code execution (RCE) vulnerability which is exploited via an attacker inserting a crafted payload into the name field under the Create New Room module.

CVSS v3
8.8
EG Score
8.9(high)
EG Risk
63(Track)
EG Risk 63/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
Severity89% × 45%
Exploitation45% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
45%
EPSS %ILE
99%
KEV
Not listed

Published

March 3, 2022

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Aug 25, 2026
No patch confirmed yet.
generic

HotelDruid: Hotel Management Software

https://www.hoteldruid.com
generic

GitHub - 0z09e/CVE-2022-22909: Hotel Druid 3.0.3 Code Injection to Remote Code Execution · GitHub

https://github.com/0z09e/CVE-2022-22909

Affected Packages

(2 across 2 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
hoteldruid3.0.1-1 ... 3.0.8-1 (6 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
hoteldruid—3.0.4-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 126 total refreshes for this CVE.

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCkaal18/CVE-2022-22909
    First seen Mar 14, 2022

    Exploits for Hotel Druid 3.0.3 - Remote Code Execution (RCE) CVE-2022-22909

    Open source ↗
  • Exploit-DBEDB-50754
    First seen Feb 18, 2022

    Hotel Druid 3.0.3 - Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoC0z09e/CVE-2022-22909
    First seen Feb 17, 2022

    Hotel Druid 3.0.3 Code Injection to Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-22909?
CVE-2022-22909 is a high vulnerability published on March 3, 2022. HotelDruid v3.0.3 was discovered to contain a remote code execution (RCE) vulnerability which is exploited via an attacker inserting a crafted payload into the name field under the Create New Room module.
When was CVE-2022-22909 disclosed?
CVE-2022-22909 was first published in the National Vulnerability Database on March 3, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-22909 actively exploited?
CVE-2022-22909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45% probability of exploitation in the next 30 days, which ranks it in the top 1.3% of all scored CVEs.
What is the CVSS score of CVE-2022-22909?
CVE-2022-22909 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2022-22909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-22909, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-22909

Explore →

Is Your Infrastructure Affected by CVE-2022-22909?

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

Start Free Scan →Browse All CVEs