dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-52834

CRITICAL · 9.3 CVSS v3.1 Published 2025-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in favethemes Homey homey allows SQL Injection.This issue affects Homey: from n/a through <= 2.4.7.

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 · moderate confidence

SQL injection vulnerability in the favethemes Homey WordPress theme allows attackers to inject malicious SQL commands through unsanitized user input. The critical CVSS 9.3 score suggests the flaw likely enables remote code execution or full database compromise via the injected SQL. All versions up to and including 2.4.7 are affected.

MitigationUpdate the Homey theme to the latest patched version as soon as feasible. If no patched version is available, locate all SQL query execution points and implement parameterized queries or prepared statements with proper input validation.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 Homey theme installation
    Check for the presence of the Homey theme directory in your WordPress installation: inspect the wp-content/themes/ folder for a 'homey' subdirectory. If using WP-CLI, run: wp theme list --status=active --format=csv
    Affected if The homey theme directory exists in wp-content/themes/
  2. Identify installed Homey theme version
    Read the theme version from the style.css file located in wp-content/themes/homey/. Look for the 'Version:' header in the file. Alternatively, if you have WP-CLI access, run: wp theme list | grep homey
    Affected if The version is 2.4.7 or lower (any version up to and including 2.4.7 is affected)
  3. Verify theme is active on the site
    Check if the Homey theme is currently active. In WordPress admin dashboard, go to Appearance > Themes, or use WP-CLI: wp theme list --status=active --format=csv
    Affected if The Homey theme shows as 'Active' in the theme list
  4. Locate SQL query execution points in the theme
    Search the theme files for direct SQL query execution patterns. Look in PHP files within wp-content/themes/homey/ for functions containing: $wpdb->prepare, $wpdb->query, $wpdb->get_results, or direct SELECT/INSERT/UPDATE/DELETE statements. Use grep or similar: grep -r '$wpdb' wp-content/themes/homey/ --include='*.php'
    Affected if The theme contains PHP files with SQL query execution that accept user input without proper sanitization or prepared statements (vulnerability is in these locations)
  5. Inspect for unsanitized user input in queries
    Examine identified SQL query files for user input sources such as $_GET, $_POST, $_REQUEST, or URL parameters used directly in queries without escaping or parameterization. Review the specific file paths returned from the previous grep search.
    Affected if User-supplied input from request parameters is being passed directly into SQL queries without using $wpdb->prepare() with placeholders or proper escaping functions

You are affected if the Homey theme is installed, active, and running version 2.4.7 or lower, with SQL query code that handles user input without parameterized queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Homey theme to the latest patched version as soon as feasible. If no patched version is available, locate all SQL query execution points and implement parameterized queries or prepared statements with proper input validation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52834 — 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-52834 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