dbcve.org
KodicmsApplication · Kodicms Kohana

CVE-2025-15392

HIGH · 8.8 CVSS v3.1 Published 2025-12-31
Fix available
A fix is available. Upgrade to after 13.82.135 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A weakness has been identified in Kohana KodiCMS up to 13.82.135. This affects the function like of the file cms/modules/pages/classes/kodicms/model/page.php of the component Search API Endpoint. Executing manipulation of the argument keyword can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

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

SQL injection vulnerability in KodiCMS up to version 13.82.135 in the Search API Endpoint. The 'like' function in cms/modules/pages/classes/kodicms/model/page.php fails to properly sanitize the 'keyword' parameter, allowing remote attackers to inject malicious SQL queries.

MitigationDisable or restrict access to the Search API endpoint until a fix is available; implement input validation and parameterized queries in the vulnerable function; consider migrating to a supported CMS platform given vendor non-responsiveness.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KodicmsApplication
Affected:<= 13.82.135

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm KodiCMS installation
    Check for the presence of Kodicms files on the server. Look for the main installation directory (commonly 'kodicms' or similar) and identify the version file. In a typical Kodicms setup, check for a version file or configuration that displays the CMS version.
    Affected if Kodicms is installed on the server.
  2. Check installed Kodicms version
    Locate and read the version information file in the Kodicms installation. Compare the version number against the affected range: <= 13.82.135. If a version file is not directly accessible, check the codebase for version strings in known version-related files or headers.
    Affected if Installed version is 13.82.135 or lower.
  3. Locate the vulnerable file
    Verify the presence of the file cms/modules/pages/classes/kodicms/model/page.php in the installation. Check if this file contains a 'like' function that handles the 'keyword' parameter from search operations.
    Affected if The vulnerable file and 'like' function exist in the codebase.
  4. Check if Search functionality is enabled
    Examine the Kodicms configuration and routing to determine if the Search API endpoint is accessible. Look for routes or modules related to search (often accessible via /search or similar endpoints) and verify whether search features are enabled in the CMS settings.
    Affected if Search API endpoint is accessible and search functionality is enabled.
  5. Verify parameter handling in the like function
    Inspect the 'like' function in cms/modules/pages/classes/kodicms/model/page.php to confirm that the 'keyword' parameter is processed without proper sanitization or parameterized queries. Look for direct string concatenation in SQL queries using the keyword input.
    Affected if The 'keyword' parameter is used in SQL queries without sanitization or parameterized binding.

The environment is affected if Kodicms version 13.82.135 or lower is installed, the vulnerable page.php file exists with the unpatched 'like' function, and the Search API endpoint is accessible and uses unsanitized keyword parameter handling.

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
Upgrade available Upgrade to a release after 13.82.135
Interim mitigation

Disable or restrict access to the Search API endpoint until a fix is available; implement input validation and parameterized queries in the vulnerable function; consider migrating to a supported CMS platform given vendor non-responsiveness.

Fix this in Kodicms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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