High · published July 26, 2025
🚨 A sneaky SQL query could slip through your defenses! Versions 17.0.0-rc1 to 17.2.2 of XWiki are vulnerable to malicious injection, making your data ripe for the taking. 🔥 Think of it like a restaurant where the chef accepts orders directly from the customers without checking the kitchen rules — you're risking a surprise dish of chaos instead of a delicious meal! An attacker could leverage this vulnerability to execute arbitrary SQL queries on your Oracle database, potentially accessing or destroying sensitive data. The consequences could be absolutely devastating, leading to data breaches or unauthorized modifications that compromise your application's integrity.
Think of it like a restaurant where the chef accepts orders directly from the customers without checking the kitchen rules — you're risking a surprise dish of chaos instead of a delicious meal! This vulnerability allows attackers to exploit the XWiki#searchDocuments APIs, which pass unvalidated queries straight to Hibernate. Despite having a restricted SELECT clause, HQL's native function support enables code injection via areas such as the WHERE clause.
An attacker could leverage this vulnerability to execute arbitrary SQL queries on your Oracle database, potentially accessing or destroying sensitive data. The consequences could be absolutely devastating, leading to data breaches or unauthorized modifications that compromise your application's integrity. Upgrade immediately to versions 16.10.6 or 17.3.0-rc-1 to patch this vulnerability. Review your database query practices to ensure proper sanitation at all levels, and consider implementing additional security measures like prepared statements. You've got this! Follow these steps and you'll be on your way to securing your XWiki installation in no time! 🛡️