dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-69304

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 Allmart allmart-core allows Blind SQL Injection.This issue affects Allmart: from n/a through <= 1.1.

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

Blind SQL Injection vulnerability in TeconceTheme Allmart's allmart-core component allows attackers to inject malicious SQL queries through unsanitized input, potentially enabling data exfiltration or database compromise. The critical CVSS score of 9.3 indicates ease of exploitation and severe potential impact.

MitigationUpdate Allmart theme to a patched version if available; otherwise, replace the theme or implement input validation/parameterized queries in the allmart-core code to neutralize the SQL injection vector.

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. Identify TeconceTheme Allmart installation
    Search for theme files named 'allmart' or 'allmart-core' in the web root directory, typically under wp-content/themes/ for WordPress or similar theme directories for other CMS platforms. Use file system search commands like 'find . -iname "*allmart*"' to locate related files.
    Affected if The Allmart theme or allmart-core component is present in the environment
  2. Determine allmart-core component version
    Locate the main allmart-core plugin or module file (commonly in includes/allmart-core.php or similar path) and check the file header or version constant for the installed version number. Also check any version.xml, readme.txt, or plugin metadata files in the theme/plugin directory.
    Affected if The version cannot be determined or is lower than the patched version (if known); if version is unknown, the component may still be vulnerable
  3. Identify SQL injection entry point
    Search the allmart-core source code for SQL query execution functions (e.g., $wpdb->prepare, mysql_query, mysqli_query, select_db) and trace back to identify where user-supplied input is passed without proper sanitization or parameterized queries. Look for GET/POST parameters used directly in SQL statements.
    Affected if User-controlled parameters (from $_GET, $_POST, or $_REQUEST) are used in SQL queries without sanitization or prepared statements
  4. Verify vulnerable parameter exposure
    Check if the affected code paths are accessible without authentication. Test by examining whether the vulnerable endpoints accept unauthenticated requests and whether the SQL injection point can be reached via HTTP requests.
    Affected if The SQL injection endpoint is accessible to unauthenticated users (no login or token required)
  5. Confirm database user privileges
    Examine the database configuration file (wp-config.php for WordPress or config.php for other setups) to determine what database privileges the application uses. The severity is higher if the database user has broad privileges (e.g., SELECT, INSERT, UPDATE, DELETE on multiple tables).
    Affected if The database user has extensive privileges beyond what is strictly necessary, allowing the injected SQL to read/modify sensitive data

If the TeconceTheme Allmart with allmart-core component is installed and user-supplied input reaches SQL queries without sanitization or prepared statements, the environment is affected by this SQL injection vulnerability.

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 Allmart theme to a patched version if available; otherwise, replace the theme or implement input validation/parameterized queries in the allmart-core code to neutralize the SQL injection vector.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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