dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13724

HIGH · 7.5 CVSS v3.1 Published 2025-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
The VikRentCar Car Rental Management System plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'month' parameter in all versions up to, and including, 1.4.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The VikRentCar WordPress plugin fails to properly escape the 'month' parameter and lacks prepared statements in its SQL queries, allowing authenticated administrators to inject arbitrary SQL commands. This time-based blind SQL injection can be exploited to exfiltrate sensitive data from the database.

MitigationUpgrade the VikRentCar plugin to a version newer than 1.4.4 where the vulnerability is patched, or implement proper SQL escaping and prepared statements for the 'month' parameter in the affected 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm VikRentCar plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for VikRentCar, or check the /wp-content/plugins/ directory for the vikrentcar folder
    Affected if VikRentCar plugin is present in the WordPress installation
  2. Identify the installed version
    In WordPress admin, go to Plugins > Installed Plugins, find VikRentCar, and note the version number displayed, or check the main plugin file header for the Version field
    Affected if Version is 1.4.4 or lower (versions up to and including 1.4.4 are affected)
  3. Verify the vulnerable parameter exists
    Inspect the plugin code for the 'month' parameter handling in files that process date or rental period inputs, typically in front-end booking forms or admin reports
    Affected if The 'month' parameter is processed without prepared statements and is directly used in SQL queries
  4. Confirm lack of SQL prepared statements
    Search plugin source files (particularly in the /models/ or /helpers/ directories) for SQL queries containing the 'month' variable and verify they do not use $wpdb->prepare() or equivalent parameterized queries
    Affected if SQL queries using the 'month' parameter do not utilize prepared statements or escaping functions

The environment is affected if VikRentCar plugin version 1.4.4 or lower is installed and the 'month' parameter is processed in SQL queries without prepared statements.

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 the VikRentCar plugin to a version newer than 1.4.4 where the vulnerability is patched, or implement proper SQL escaping and prepared statements for the 'month' parameter in the affected code.

Recommended fix Moderate confidence

Latest version after 1.4.4 (contact vendor for exact fixed release)

  1. Check for plugin updates in WordPress admin dashboard under Plugins > All Plugins
  2. If an update is available for VikRentCar, update to the latest version
  3. If no update is visible, contact the plugin vendor (E4J/VikRentCar) directly to request the security patch
  4. Verify the update resolves the issue by confirming the 'month' parameter is now properly sanitized/parameterized
  5. Consider reviewing other plugin parameters for similar SQL injection vulnerabilities

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

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-13724 — 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-13724 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