CVE-2025-10115
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 · uneditedA vulnerability was determined in SiempreCMS up to 1.3.6. This affects an unknown part of the file user_search_ajax.php. This manipulation of the argument name/userName causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceSQL injection vulnerability in SiempreCMS up to version 1.3.6 in the user_search_ajax.php file. The name/userName parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SiempreCMS versionLocate the version file or header in the CMS installation (commonly in a version.php, composer.json, or admin dashboard about page). Compare the version number to 1.3.6.Affected if The installed version is 1.3.6 or earlier.
-
Locate user_search_ajax.php fileSearch the web root directory for the file user_search_ajax.php. Common paths may include /ajax/, /admin/ajax/, or /scripts/ subdirectories.Affected if The file exists in the deployed application.
-
Verify the userName parameter handlingOpen user_search_ajax.php and locate the code that handles the name or userName parameter. Search for direct insertion of this parameter into SQL queries without sanitization or prepared statements.Affected if The parameter is used directly in SQL queries without escaping, sanitization functions, or prepared statement binding.
-
Check for input validation functionsInspect the code around the SQL query construction for functions like mysqli_prepare, PDO::prepare, mysql_real_escape_string, htmlspecialchars, or other input validation routines applied to the userName parameter.Affected if No parameterized queries or escaping functions are found in the code handling the userName parameter in user_search_ajax.php.
You are affected if your installed SiempreCMS version is 1.3.6 or earlier AND the user_search_ajax.php file contains the vulnerable code that passes the userName parameter directly into SQL queries without prepared statements or escaping.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade SiempreCMS to a version beyond 1.3.6 that contains the patched code, or implement parameterized queries/prepared statements for the userName parameter in user_search_ajax.php to prevent SQL injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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