Skip to main content
VulnerabilityPublished

CVE-2025-45777: CVE_ID · Improper Authentication

Affects CVE_IDSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% 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 25 Jul 2025

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubedwin-0990/CVE_IDpkg:github/edwin-0990/CVE_IDOther threatsAffected
  • =2.0
Fixed in–

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

AI-suggested

Given the absence of an official patch, European organizations and users of the affected platform should take several practical steps: 1) Immediately review and audit the OTP implementation for logic flaws or improper validation of authentication requests. 2) Implement additional layers of authentication or anomaly detection, such as device fingerprinting or behavioral analytics, to detect suspicious login attempts. 3) Enforce strict rate limiting and monitoring on OTP submission endpoints to prevent automated or crafted request abuse. 4) Educate users about potential phishing or social engineering attacks that could exploit authentication weaknesses. 5) If possible, disable or restrict access to the vulnerable OTP mechanism until a secure patch or update is available. 6) For organizations handling user data from this platform, ensure incident response plans are updated to quickly address potential unauthorized access. 7) Engage with the vendor or platform maintainers to obtain timely patches or mitigations. 8) Conduct penetration testing focused on authentication bypass scenarios to proactively identify similar weaknesses.

Description

An issue in the OTP mechanism of Chavara Family Welfare Centre Chavara Matrimony Site v2.0 allows attackers to bypass authentication via supplying a crafted request.

References

Community reviews

Loading reviews…