CVE-2025-54428: musombi123 RevelaCode-Backend · Insufficiently Protected Credentials
Affects musombi123 RevelaCode-BackendSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.0.1 as a priority.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Upgrade musombi123/RevelaCode-Backend to 1.0.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmusombi123/RevelaCode-Backendpkg:github/musombi123/RevelaCode-BackendOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediate rotation of all MongoDB Atlas credentials that were exposed in the public repository to invalidate any leaked secrets.
- Upgrade RevelaCode-Backend to version 1.0.1 or later, which addresses this vulnerability by removing embedded credentials.
- Implement a robust secret management strategy using dedicated tools such as HashiCorp Vault, Doppler, or AWS Secrets Manager to store and access database credentials securely, avoiding hardcoding secrets in source code.
- Conduct thorough audits of MongoDB Atlas access logs to identify any unauthorized or suspicious access patterns since the exposure.
- Enforce network-level access controls on MongoDB Atlas instances, such as IP whitelisting and VPC peering, to restrict database access to trusted environments only.
- Integrate automated code scanning tools in the CI/CD pipeline to detect accidental credential commits before code is merged or deployed.
- Educate development teams on secure coding practices, emphasizing the risks of embedding secrets in code repositories.
- Consider implementing multi-factor authentication (MFA) and role-based access controls (RBAC) for database access to minimize the impact of credential exposure.
Description
RevelaCode is an AI-powered faith-tech project that decodes biblical verses, prophecies and global events into accessible language. In versions below 1.0.1, a valid MongoDB Atlas URI with embedded username and password was accidentally committed to the public repository. This could allow unauthorized access to production or staging databases, potentially leading to data exfiltration, modification, or deletion. This is fixed in version 1.0.1. Workarounds include: immediately rotating credentials for the exposed database user, using a secret manager (like Vault, Doppler, AWS Secrets Manager, etc.) instead of storing secrets directly in code, or auditing recent access logs for suspicious activity.