Skip to main content
CVE-2021-42949VulnerabilityPublished Updated

CVE-2021-42949: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
7.2% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubdhammon/HotelDruid-CVE-2021-42949pkg:github/dhammon/HotelDruid-CVE-2021-42949Other threatsAffected
  • =3.0.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediate mitigation should include implementing network-level protections such as Web Application Firewalls (WAFs) to detect and block brute-force attempts targeting session tokens. 2. Monitor authentication logs for unusual patterns indicative of brute-force token guessing. 3. Restrict access to the HotelDruid management interface to trusted IP addresses or VPN-only access to reduce exposure. 4. If possible, disable or limit the use of the vulnerable login component until a patch is available. 5. Engage with the software vendor or community to obtain updates or patches addressing the session token generation flaw. 6. Implement multi-factor authentication (MFA) at the application or network level to add an additional layer of security beyond session tokens. 7. Conduct regular security assessments and penetration testing focused on authentication mechanisms. 8. Educate staff about the risks and signs of compromise related to authentication bypass attacks. These steps go beyond generic advice by focusing on compensating controls and proactive monitoring tailored to the specific vulnerability and the hospitality sector environment.

Description

The component controlla_login function in HotelDruid Hotel Management Software v3.0.3 generates a predictable session token, allowing attackers to bypass authentication via bruteforce attacks.

References

Community reviews

Loading reviews…