Search: “sql injection”

4 stories

Searchkeyword smart Sortlatest hot importance relevance

DomainAll Cyber AIWindow24h 3d 7d 30d AllIn the wild Important only Show duplicates

CategoryAll Vulnerability 552 Exploit / PoC 191 Ransomware 162 Data breach 126 Malware 73 Threat actor 31 AI safety & security 15 Advisory 14 Phishing & fraud 14 Policy & legal 13 Industry 5 Research 4 Tools 3 AI tools & infra 2

SeverityAll critical 635 high 319 medium 195 low 39 info 18

1-15 August 2026 Cyber Attacks Timeline Infographic

Hackmageddon's infographic visualizes 108 attacks from August 1-15, 2026, with ransomware in 17 incidents and the US most targeted.

The infographic summarizes 108 confirmed incidents for August 1-15, 2026, an attack reported every 3.3 hours, with 90 of 108 (83.3%) driven by cybercrime. Ransomware appeared in 17 incidents, account takeover in 12, SQL injection in 8 and authentication bypass in 5. The United States was the most-targeted country with 34 of 92 country mentions, and Public Administration led sector targeting with 25 of 139 sector mentions.

HackmageddonSep 2, 09:46 UTC · 13d agoResearch 2 sources

AI AppSec tools agree on just 5% of security findings

Contrast Security report finds 42 confirmed exploit attempts per application monthly and three AI scanners agreeing on only 5% of findings.

Contrast Security's AppSec Overflow 2026 report, drawing on telemetry from hundreds of thousands of production applications and APIs, found adversaries touch the average application every four minutes with 42 confirmed viable exploit attempts per application monthly, led by untrusted deserialization, path traversal, and method tampering. Legacy flaws Log4Shell and Spring4Shell remain widespread, mean time to exploit fell from over two years in 2018 to under three weeks for most 2025 exploited vulnerabilities, and average critical fix time is 92 days. Three AI scanners set on the same codebase agreed on only 5% of findings, and triaging a 2-million-line codebase scan cost roughly $128,000 versus $315 in API charges. Among exploited CVEs in the dataset, 82% of KEV-listed entries carried EPSS scores of 90% or higher, while CVE-2006-1547 and CVE-2023-38180 were confirmed exploited despite EPSS scores under 25%.

Help Net SecurityAug 31, 00:00 UTC · 16d agoResearch in the wildCVE-2006-1547 CVE-2023-381801

$20 per zero-day is already the WordPress plugin reality

TrendAI and CHT Security used an AI pipeline to find over 300 verified WordPress plugin zero-days at roughly $20 per vulnerability.

A pipeline built in three days by TrendAI and CHT Security, presented at Ekoparty Miami, paired AI-driven static analysis with automated Docker provisioning and Chrome DevTools MCP dynamic verification to surface more than 300 critical zero-days in WordPress plugins within 72 hours. The run consumed about 222 million tokens across 95 tasks, averaging roughly $20 per verified vulnerability, with findings including pre-auth RCE, SQL injection, privilege escalation, SSRF, and an AI-assembled downgrade attack chain. Dynamic verification eliminated over 80% of false positives, but manual review at 30-60 minutes per finding remains the bottleneck, straining ZDI and NIST triage backlogs.

Help Net SecurityAug 24, 04:21 UTC · 23d agoResearch1

Harnessing LLMs for Automating BOLA Detection

Unit 42's BOLABuster methodology uses LLMs to automate detection of broken object-level authorization vulnerabilities, uncovering flaws in Grafana, Harbor, and Easy!Appointments.

Palo Alto Unit 42 details BOLABuster, a methodology combining large language models with heuristics to automate detection of broken object-level authorization (BOLA) flaws, which traditional fuzzing and static analysis struggle to find. The approach uses LLM reasoning to understand application logic, map endpoint dependency relationships, and generate and interpret test cases. It found CVE-2024-1313 in Grafana, CVE-2024-22278 in Harbor, and 15 CVEs in Easy!Appointments. The team is continuing to hunt for BOLAs in open-source and internal projects.

Palo Alto Unit 42Aug 17, 12:34 UTC · 29d agoResearch CVE-2024-1313 CVE-2024-22278 CVE-2023-3285+14 CVEs