dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22699

CRITICAL · 9.0 CVSS v3.1 Published 2025-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/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 shinetheme Traveler Code traveler-code.This issue affects Traveler Code: from n/a through < 3.1.2.

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 confidence

A SQL injection vulnerability exists in the Traveler Code theme (versions before 3.1.2) due to improper neutralization of special elements in SQL commands. This critical flaw (CVSS 9) allows remote attackers to manipulate database queries by injecting malicious SQL code through unsanitized input parameters.

MitigationUpgrade Traveler Code to version 3.1.2 or later. If immediate patching is not possible, implement a WAF rule to block SQL injection patterns and audit the codebase for vulnerable query constructions using direct string concatenation.

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Traveler Code theme version
    Navigate to WordPress admin > Appearance > Themes and locate the Traveler Code theme. The version number is displayed in the theme details panel. Alternatively, check the style.css file in the theme directory for the 'Version:' comment header.
    Affected if The installed version is below 3.1.2 (e.g., 3.1.1, 3.0.x, 2.x)
  2. Identify theme directory path
    Access the wp-content/themes directory via FTP or file manager. Locate the traveler-code or stm-traveler theme folder. Note the exact folder name used in your installation.
    Affected if The Traveler Code theme folder exists and contains theme files with version information below 3.1.2
  3. Inspect theme functions for SQL query construction
    Open the functions.php file in the Traveler Code theme directory. Search for database query functions (wpdb->prepare, $wpdb->query, WP_DB::prepare) that may use direct user input. Look for parameters like $_GET, $_POST, or $_REQUEST being passed into SQL queries without proper escaping or prepared statements.
    Affected if The theme contains SQL queries that incorporate request parameters ($_GET, $_POST, $_REQUEST) directly into queries without using $wpdb->prepare() or proper escaping functions
  4. Verify unsanitized input parameters
    Examine the theme's PHP files for vulnerable parameter handling. Common injection points include search parameters, filter options, ID parameters in URLs, and form submissions. Search for patterns like $_GET['s'], $_GET['id'], $_REQUEST['location'] used in database operations.
    Affected if User-supplied input from $_GET, $_POST, or $_REQUEST is used in SQL queries without sanitization via prepared statements or esc_sql() function

Your environment is affected if the Traveler Code theme version is below 3.1.2 AND the theme contains SQL queries that process unsanitized user input from request parameters.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Traveler Code to version 3.1.2 or later. If immediate patching is not possible, implement a WAF rule to block SQL injection patterns and audit the codebase for vulnerable query constructions using direct string concatenation.

Recommended fix High confidence

3.1.2

  1. Check the current version of Traveler Code installed on the site.
  2. Create a complete backup of the WordPress site, including database and files.
  3. Update Traveler Code to version 3.1.2 or the latest subsequent release.
  4. Verify the update was successful and ensure the site functions correctly.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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