JoomlArt Exposes 22,477 User Accounts via Mis‑configured Jira Ticket
What Happened – In January 2018 a Jira ticket inadvertently contained a dump of 22,477 unique customer records from JoomlArt’s iJoomla and JomSocial services. The exposed data included usernames, email addresses, purchase histories and passwords stored as unsalted MD5 hashes.
Why It Matters for Trust & Control Assurance
- Highlights the risk of weak credential‑storage practices and the need for strong hashing algorithms.
- Shows how a simple misconfiguration in an internal ticketing system can become a data‑exposure vector, underscoring the value of continuous monitoring of privileged tools.
- Demonstrates the importance of documenting and evidencing access‑control policies to satisfy audit requirements.
Who Is Affected – SaaS and web‑template providers (technology sector) that store customer credentials and use internal collaboration tools.
Recommended Actions
- Replace MD5 password hashes with a modern, salted algorithm (e.g., bcrypt, Argon2).
- Harden access controls and enable detailed logging for all ticketing and documentation platforms.
- Map the incident to your control‑assurance framework, collect evidence of remediation, and update audit‑readiness artifacts.
Technical Notes – The breach resulted from a misconfiguration that exposed a Jira ticket; no public exploit or CVE is involved. Exposed data types: email, name, username, MD5‑hashed password, payment history. Source: Have I Been Pwned – JoomlArt breach