CVE-2025-32303
Blind SQL Injection in WPCHURCH Plugin up to
Publication date: 2026-01-07
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mojoomla | wpchurch | to 2.7.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Blind SQL Injection in the Mojoomla WPCHURCH plugin, which means that an attacker can inject malicious SQL commands into the database queries without direct visibility of the query results. It occurs due to improper neutralization of special elements used in SQL commands, allowing unauthorized manipulation of the database.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to extract sensitive information from the database, potentially leading to data breaches. It can also cause partial denial of service by impacting database availability. The CVSS score indicates high confidentiality impact and low availability impact, meaning sensitive data could be exposed without necessarily disrupting service completely.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthenticated attackers to execute arbitrary SQL queries on the database, potentially leading to data theft or unauthorized database manipulation. Such data breaches can result in non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and mandate breach notification. Therefore, exploitation of this vulnerability could lead to violations of these regulations due to compromised data confidentiality and integrity. [1]
What immediate steps should I take to mitigate this vulnerability?
Users are strongly advised to implement Patchstackβs mitigation rule to block attacks targeting this vulnerability until an official fix is released, as no official patch or fixed version is currently available. [1]