CVE-2025-54720
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in SteelThemes Nest Addons nest-addons allows SQL Injection.This issue affects Nest Addons: from n/a through <= 1.6.3.
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 confidenceSQL Injection vulnerability in SteelThemes Nest Addons plugin allows attackers to inject malicious SQL commands through unsanitized user inputs in database queries, potentially enabling unauthorized data access, modification, or deletion.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Nest Addons plugin is installedLocate the SteelThemes Nest Addons plugin in your WordPress installation under wp-content/plugins/ directory, or check via WordPress admin plugin listAffected if The plugin directory exists and the plugin is active on the site
-
Identify installed version numberCheck the plugin's main PHP file header for 'Version:' comment, or view the plugin in WordPress admin which displays the version numberAffected if The version number is 1.6.3 or lower (all versions through 1.6.3 are affected)
-
Verify plugin is accessible to unauthenticated usersTest accessing the plugin's publicly facing functionality without logging in - the vulnerability is exploitable remotely without authenticationAffected if The plugin endpoints are reachable by unauthenticated visitors or API requests
-
Inspect plugin files for direct database query usageSearch plugin PHP files for direct MySQL query patterns (mysql_query, $wpdb->query, $wpdb->prepare without proper sanitization of $_GET, $_POST, or $_REQUEST variables)Affected if Code contains database queries that incorporate user input without using prepared statements or sanitization functions
-
Review access logs for SQL injection patternsExamine web server access logs for unusual SQL syntax in query parameters targeting the Nest Addons plugin URLs (GET/POST requests with quotes, UNION, SELECT, OR 1=1 patterns)Affected if Logs show SQL injection attempts against Nest Addons endpoints, indicating active exploitation attempts
A user is affected if the SteelThemes Nest Addons plugin version 1.6.3 or lower is installed and active on their WordPress site, since all versions through 1.6.3 contain the SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to the latest version of Nest Addons after the patched release is available, and implement parameterized queries or prepared statements for all database operations using user-supplied input.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54720 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54720 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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