Loading story…
A critical SQL injection vulnerability (CVE-2025-58450) has been identified in pREST versions prior to 2.0.0-rc3. The flaw allows remote attackers to exploit inadequate input validation, potentially compromising PostgreSQL databases. Users are advised to update to version 2.0.0-rc3 or later and review input validation across all API endpoints.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
1 event from the most recent confirmed update back to the earliest known activity.
Initial story creation
5 references tracked. Mallory keeps watching after this page renders.
securityonline.info
Open sourcesecurityonline.info
Open sourcesecurityonline.info
Open sourcesecurityonline.info
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Drupal released security updates for **CVE-2026-9082**, a highly critical SQL injection flaw in Drupal core that affects websites using **PostgreSQL** databases. The vulnerability stems from improper neutralization of special characters in user input within Drupal's database API, allowing an unauthenticated remote attacker to send crafted requests that can trigger SQL injection. Successful exploitation could lead to **information disclosure**, **privilege escalation**, and in some environments potentially **remote code execution**. Drupal and downstream defenders urged administrators to upgrade to fixed versions **10.4.10**, **10.5.10**, **10.6.9**, **11.1.10**, **11.2.12**, or **11.3.10**, while manual patches were also issued for unsupported **8.9** and **9.5** branches; the flaw's severity was raised to **CVSS 9.8** after initial scoring understated the risk.
Jul 24, 2026
A critical remote code execution vulnerability, tracked as CVE-2025-13780, was discovered in *pgAdmin 4*, the widely used open-source PostgreSQL database management tool. The flaw allows attackers to bypass security filters in the plain-text restore feature by inserting unexpected whitespace characters, enabling the execution of arbitrary shell commands on the host server through maliciously crafted SQL dump files. The vulnerability affects pgAdmin 4 versions prior to 9.11 and was found to stem from an inadequate regular expression filter that failed to block dangerous commands effectively. Security researchers at EndorLabs identified the issue and reported that attackers could exploit this weakness to gain unauthorized access and potentially take over affected servers. In response, the pgAdmin development team released version 9.11, which implements the `\restrict` command to disable hazardous operations during the restore process, fundamentally improving the security model by enforcing restrictions at the execution level rather than relying solely on input filtering. Users are strongly advised to update to the latest version to mitigate the risk of exploitation.
Jun 29, 2026
A critical SQL injection flaw tracked as **`CVE-2026-12076`** has been disclosed in **Raytha CMS**, with confirmed impact on version **1.5.2**. The vulnerability resides in the platform’s **OData filter parsing pipeline** and allows a remote, unauthenticated attacker to execute arbitrary SQL statements against the underlying **PostgreSQL** database. Successful exploitation could lead to full database compromise, including extraction of stored credentials and other sensitive data. The issue has been rated **CVSS 4.0 9.3 (Critical)** and is considered remotely exploitable. **CERT Polska** coordinated disclosure and credited **Arkadiusz Marta** for the report, but said attempts to contact the vendor were unsuccessful, leaving uncertainty over whether additional versions are affected. Published guidance recommends upgrading to a patched release when available, applying SQL injection defenses, restricting database privileges, and monitoring database logs for suspicious activity.
Jun 30, 2026