A series of recent technical write-ups and research articles highlight the ongoing risks posed by web application vulnerabilities, including source code disclosure, SQL injection, and insecure direct object references (IDOR). One case study demonstrates how a shopping website's backup files, accessible via a hidden directory, exposed sensitive source code and hard-coded database credentials due to improper directory listing and robots.txt configuration. Another firsthand account details a significant financial loss after a modern Spring Boot application suffered a SQL injection attack, bypassing ORM protections and security audits, which allowed an attacker to manipulate discount codes and process fraudulent transactions. These incidents underscore that even contemporary, well-maintained applications remain susceptible to classic vulnerabilities when security controls are inconsistently applied or overlooked.
In addition to these real-world breaches, a technical explainer on IDOR vulnerabilities outlines why such flaws persist in modern API-driven environments, emphasizing the challenges of reliably enforcing object-level authorization. The article explains how IDORs often arise from overlooked workflow edges and inconsistent ownership validation, making them difficult to detect with standard security testing. Collectively, these reports serve as a reminder that legacy vulnerabilities like SQL injection and IDOR continue to threaten organizations, and that secure coding practices, comprehensive testing, and vigilant configuration management are essential to mitigating these risks.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
A shopping website's accessible /backup directory, discoverable by fuzzing and referenced in robots.txt, had directory listing enabled and exposed a java.bak file. The backup file disclosed Java source code containing hardcoded PostgreSQL credentials for a local database instance.
Following the attack, the organization implemented strict input validation, removed native queries, disabled multi-statement execution, added security tests, and conducted a full code audit. It also hired a dedicated security engineer and enforced security checklists in code reviews.
Attackers exploited the vulnerable discount search to dump discount codes, modify discount percentages, and apply 100% discounts to hundreds of orders. The incident resulted in about $47,000 in fraudulent transactions, along with reputational damage and scrutiny from payment processors.
A modern Spring Boot application had a SQL injection vulnerability in a native SQL query used by an admin discount code search feature. The endpoint was misconfigured to be publicly accessible and lacked proper input validation, reintroducing a classic injection flaw despite use of JPA and Hibernate.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
infosecwriteups.com
Open sourceaikido.dev
Open sourceosintteam.blog
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.