CVE-2024-51051: avscms · n/a
Affects avscmsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2024
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubavscms/avscmspkg:github/avscms/avscmsOther 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
1. Immediately change the default Administrator credentials in AVSCMS v8.2.0 to strong, unique passwords following best practices (e.g., minimum length, complexity, no reuse). 2. Implement multi-factor authentication (MFA) for administrative accounts to add an additional security layer. 3. Restrict administrative access to trusted IP addresses or VPNs to reduce exposure. 4. Monitor logs for unusual login attempts or access patterns indicative of brute force or unauthorized access. 5. Disable or remove any unused default accounts or services that may present additional attack vectors. 6. Conduct a thorough security audit of AVSCMS deployments to identify and remediate other potential misconfigurations. 7. Stay alert for official patches or updates from AVSCMS vendors and apply them promptly once available. 8. Educate administrators and users about the risks of default credentials and enforce policies to prevent their use. 9. Consider network segmentation to isolate CMS servers from critical internal systems to limit potential lateral movement. 10. Employ web application firewalls (WAFs) to detect and block suspicious activities targeting the CMS.
Description
AVSCMS v8.2.0 was discovered to contain weak default credentials for the Administrator account.