dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-69305

CRITICAL · 9.3 CVSS v3.1 Published 2026-02-20
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 TeconceTheme Crete Core crete-core allows Blind SQL Injection.This issue affects Crete Core: from n/a through <= 1.4.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 confidence

A blind SQL injection vulnerability exists in TeconceTheme Crete Core (crete-core) version 1.4.3 and below. The vulnerability allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized database access, data exfiltration, or privilege escalation.

MitigationUpgrade Crete Core to the latest version which should contain patched code with proper input sanitization and parameterized queries. If no update is available, manually audit and refactor all database queries to use prepared statements.

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. Locate the Crete Core installation
    Identify the crete-core plugin or theme files in your WordPress installation (commonly in /wp-content/themes/crete/ or /wp-content/plugins/crete-core/). Check for a version file or header in the main plugin/theme PHP file.
    Affected if The crete-core plugin or theme is present in the WordPress installation.
  2. Determine the installed version
    Open the main PHP file of crete-core (often named index.php, main.php, or crete-core.php) and look for a version comment or constant defined near the top (for example: 'Version: 1.4.3' or 'define("CRETE_VERSION", "...")').
    Affected if The version number found is 1.4.3 or lower.
  3. Identify database query code
    Search the crete-core files for direct SQL query execution patterns such as $wpdb->prepare(), $wpdb->query(), or raw SELECT/INSERT/UPDATE/DELETE statements using $wpdb->. Examine files in includes/ or classes/ directories where database interactions typically occur.
    Affected if Database queries exist that use string concatenation or interpolation for building SQL clauses without proper sanitization functions like $wpdb->prepare() or esc_sql().
  4. Check for unsanitized user input in queries
    Review the database query code identified in the previous step. Look for parameters that receive input from $_GET, $_POST, $_REQUEST, or URL segments (like $_GET['id'], $_GET['slug'], etc.) and are directly inserted into SQL strings.
    Affected if User-supplied input from $_GET, $_POST, or URL parameters is directly concatenated into SQL queries without using $wpdb->prepare() or esc_sql().
  5. Audit accessible endpoints
    Identify which PHP files handle HTTP requests (look for files that process ?action=, ?page=, or AJAX handlers). Determine if these endpoints call the vulnerable query code and are accessible without authentication.
    Affected if Endpoints exist that pass unsanitized user input to the vulnerable database query functions and are reachable over the network.

You are affected if crete-core version 1.4.3 or lower is installed AND your environment contains database queries that directly incorporate user input from HTTP requests without using prepared statements or sanitization functions.

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

Upgrade Crete Core to the latest version which should contain patched code with proper input sanitization and parameterized queries. If no update is available, manually audit and refactor all database queries to use prepared statements.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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