Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

CVE-2025-64459 is a critical SQL injection vulnerability in the Django web framework’s ORM. It affects Django 5.1 versions earlier than 5.1.14, Django 4.2 versions earlier than 4.2.26, and Django 5.2 versions earlier than 5.2.8. Earlier, unsupported series such as 5.0.x, 4.1.x, and 3.2.x were not evaluated and may also be affected, which makes legacy deployments especially risky.

CVE-2025-64095 is a critical unauthenticated file-upload vulnerability affecting DNN (DotNetNuke) versions prior to 10.1.1. The flaw exists in the platform’s default HTML editor provider, where upload validation and authorization checks were insufficient. Attackers can upload files and overwrite existing content without credentials, enabling page defacement, malicious script injection, and in some environments stored cross-site scripting (XSS).

CVE-2025-55752 is a path traversal vulnerability in Apache Tomcat. It comes from a regression introduced during a past bug fix. Because of this flaw, Tomcat normalizes URLs before decoding them, which lets attackers craft requests that bypass access controls and reach restricted directories like /WEB-INF/ and /META-INF/. In deployments where HTTP PUT is enabled, an attacker could upload files through this path and potentially gain remote code execution (RCE).

In our day-to-day work and conversations with security experts, one concern comes up regularly: how consistent is our WAF protection? Our answer is always the same: not as much as you think. The truth is that in the case of enterprises, web application firewall (WAF) coverage is rarely uniform. Protection is often a mixed bag of products from different vendors, managed by separate teams, each guarding only part of the attack surface.

Security teams need automation, clarity, and speed to stay ahead. This month’s updates continue to refine the CyCognito experience so you can maintain an accurate asset inventory, pivot through investigations quickly, and share the right information with stakeholders. In the past few weeks we delivered improvements across automation (including Action Rules), APIs improvements, new investigation and management options, and reporting controls for PDFs. Below is a detailed look at what is new.

Visibility without control is only half the battle. To truly stay ahead of attackers, security teams need precise access, trusted data, and efficient workflows they can rely on. That’s why we’re continuing to enhance the CyCognito platform with features that improve transparency, streamline operations, and put more power in your hands.

Today we’re releasing findings from a statistical sample of over 2 million internet-exposed assets, across on-prem, cloud, APIs, and web apps, discovered and analyzed by the CyCognito platform.

In today’s high-stakes cybersecurity landscape, one truth stands out: if you can’t see it, you can’t secure it. And if you can’t act on what you see, you’re no better off. That’s why we’re focused on delivering continuous improvements that help security teams move faster, see further, and reduce risk where it matters most.

CyCognito is always seeking additional methods to discover customer external-facing assets. One such resource is an integration with content delivery network (CDN) management systems. Many organizations manage most or all their DNS records with CDNs, as they provide IT and security teams with centralized management visibility.