CVE-2025-6495
BaseFortify
Publication date: 2025-07-29
Last updated on: 2025-07-29
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| bricksbuilder | bricks | 1.12.4 |
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?
The Bricks theme for WordPress has a blind SQL Injection vulnerability via the 'p' parameter in all versions up to and including 1.12.4. This occurs because the user-supplied 'p' parameter is not properly escaped or prepared in the SQL query, allowing unauthenticated attackers to append additional SQL queries. This can be exploited to extract sensitive information from the database.
How can this vulnerability impact me? :
This vulnerability can allow unauthenticated attackers to extract sensitive information from your WordPress site's database by injecting malicious SQL queries through the 'p' parameter. This can lead to data breaches and exposure of confidential data.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability, update the Bricks theme for WordPress to a version later than 1.12.4 where the blind SQL Injection issue via the 'p' parameter is fixed. Additionally, consider testing updates on staging or local environments before deploying to production to ensure compatibility and stability. [1]