CVE-2025-51535: Austrian Archaeological Institute OpenAtlas · Use of Default Credentials
Source CVE Database V5
Not known to be exploited · CVSS 9.1 Critical.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 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
AI-suggested
Organizations should immediately conduct an inventory to identify deployments of OpenAtlas version 8.11.0. Since no official patches are currently linked, it is critical to engage with the Austrian Archaeological Institute or software maintainers to obtain or request a security update addressing CVE-2025-51535. In the interim, restrict access to the vulnerable application to only trusted, high-privilege users and enforce the principle of least privilege to minimize the number of accounts with elevated rights. Implement network segmentation and firewall rules to limit exposure of the OpenAtlas service to only necessary internal networks. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the application. Conduct thorough logging and monitoring of database queries and application logs to detect anomalous activities indicative of exploitation attempts. Additionally, perform regular security assessments and penetration testing focused on SQL injection vectors. Educate privileged users about the risks of SQL injection and enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. Finally, prepare an incident response plan specific to database compromise scenarios to enable rapid containment and recovery if exploitation occurs.
Description
Austrian Archaeological Institute (AI) OpenAtlas v8.11.0 as discovered to contain a SQL injection vulnerability.