dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-6495

HIGH · 7.5 CVSS v3.1 Published 2025-07-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Bricks theme for WordPress is vulnerable to blind SQL Injection via the ‘p’ parameter in all versions up to, and including, 1.12.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Bricks theme for WordPress versions up to 1.12.4 contains a blind SQL injection vulnerability in the 'p' parameter. The vulnerability exists due to insufficient input sanitization and lack of prepared SQL statements, allowing unauthenticated attackers to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate to version 1.12.5 or later which patches this vulnerability. If immediate patching is not possible, consider disabling the theme or implementing a WAF rule to filter malicious 'p' parameter requests until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Bricks theme is installed
    Navigate to Appearance > Themes in WordPress admin, or inspect the /wp-content/themes/ directory for the bricks theme folder
    Affected if Bricks theme is present and active in the WordPress installation
  2. Identify installed Bricks version
    Check the version number in the theme header (style.css file in /wp-content/themes/bricks/) or via WordPress theme details panel. The version is typically listed in the comment block at the top of style.css
    Affected if Version is 1.12.4 or lower (any version up to and including 1.12.4)
  3. Verify 'p' parameter is accessible
    Test if the 'p' parameter is processed by making a request to the site with ?p=1 appended to any URL (e.g., example.com/?p=1). This parameter is used for WordPress posts and is handled by the theme when loading post content
    Affected if The site responds to the 'p' parameter and the Bricks theme processes post queries without additional access controls
  4. Check for WAF or parameter filtering
    Review any web application firewall rules, security plugins, or proxy configurations that may filter or block SQL injection attempts in the 'p' parameter
    Affected if No WAF, security plugin, or filtering is in place to sanitize the 'p' parameter

You are affected if Bricks theme versions 1.12.4 or lower are installed and active, and the 'p' parameter is accessible without sanitization or protective filtering.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.12.5 or later which patches this vulnerability. If immediate patching is not possible, consider disabling the theme or implementing a WAF rule to filter malicious 'p' parameter requests until the update can be applied.

Recommended fix High confidence

Bricks theme version 1.12.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Locate the Bricks theme
  4. Check the current version of the Bricks theme in the theme details
  5. If the version is 1.12.4 or lower, update to the latest version of the Bricks theme
  6. Verify the update was successful by checking the theme version after updating
Caveat Review theme settings and customizations after upgrade as a standard best practice

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6495 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6495 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data