CVE-2025-14973
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 · uneditedThe Recipe Card Blocks Lite WordPress plugin before 3.4.13 does not sanitize and escape a parameter before using it in a SQL statement, allowing contributors and above to perform SQL injection attacks.
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 confidenceThe Recipe Card Blocks Lite WordPress plugin before version 3.4.13 fails to sanitize and escape a parameter before using it in a SQL query, allowing authenticated users with contributor-level or higher privileges to inject malicious SQL code.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Recipe Card Blocks Lite is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Recipe Card Blocks Lite' in the list.Affected if Plugin is present in the WordPress installation
-
Check installed plugin versionIn the Plugins list, locate Recipe Card Blocks Lite and view the version number displayed beneath the plugin name. Alternatively, open /wp-content/plugins/recipe-card-blocks-lite/readme.txt and check the 'Stable tag' entry.Affected if Version number is below 3.4.13 (for example, 3.4.12, 3.4.10, etc.)
-
Confirm user has contributor-level or higher accessIn WordPress admin, go to Users > All Users and check the role assigned to your account. Contributors, Authors, Editors, and Administrators all have contributor-level or higher privileges.Affected if Your user account has a role of Contributor, Author, Editor, or Administrator
-
Identify vulnerable parameter usageReview plugin functionality that accepts user input and passes it to database queries (typically in recipe submission, import, or search features). Check plugin source files in /wp-content/plugins/recipe-card-blocks-lite/ for direct SQL queries using $wpdb without proper prepare() or sanitization.Affected if The plugin processes SQL queries with parameters that accept user-supplied input without sanitization
Your environment is affected if the Recipe Card Blocks Lite plugin is installed with a version earlier than 3.4.13 and you have users with contributor-level or higher WordPress privileges.
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.
dbcve · scopedUpdate the Recipe Card Blocks Lite plugin to version 3.4.13 or later to patch the SQL injection vulnerability.
3.4.13 or later
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate 'Recipe Card Blocks' (or 'Recipe Card Blocks Lite')
- Check the current version installed
- If the version is below 3.4.13, click 'Update Now' to upgrade to the latest version
- Alternatively, download version 3.4.13 or later from the WordPress plugin repository and upload manually
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14973 — 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-14973 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