dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2199

CRITICAL · 9.3 CVSS v4.0 Published 2025-03-17
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
SQL injection vulnerability in the Innovación y Cualificación local administration plugin ajax.php. This vulnerability allows an attacker to obtain, update and delete data from the database by injecting an SQL query in ‘searchActionsToUpdate’, ‘searchSpecialitiesPending’, ‘searchSpecialitiesLinked’, ‘searchUsersToUpdateProfile’, ‘training_action_data’, ‘showContinuingTrainingCourses’ and ‘showUsersToEdit’ in /local/administration/ajax.php.

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 the Innovación y Cualificación local administration plugin's ajax.php file. Multiple parameters including 'searchActionsToUpdate', 'searchSpecialitiesPending', 'searchSpecialitiesLinked', 'searchUsersToUpdateProfile', 'training_action_data', 'showContinuingTrainingCourses', and 'showUsersToEdit' fail to properly sanitize user input, allowing attackers to inject arbitrary SQL queries to read, modify, or delete database contents.

MitigationImplement prepared statements/parameterized queries for all listed parameters in ajax.php. If immediate patching is unavailable, disable the affected plugin or restrict access to ajax.php via web server configuration while awaiting an official vendor patch.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 if the plugin is installed
    Locate the plugin directory in the LMS (likely Moodle) installation. Common paths include /local/ or /local/icualification/ or search for directories containing 'Innovación' or 'icualification' in the name.
    Affected if The 'Innovación y Cualificación' local admin plugin directory exists in the LMS installation.
  2. Determine the installed plugin version
    Check the plugin's version.php or version.info file within the plugin directory for the version number.
    Affected if You cannot determine a version or the installed version is lower than the patched version (the vendor has not published an exact version number for this advisory).
  3. Verify ajax.php exists and is accessible
    Locate the ajax.php file within the plugin directory structure, typically under /local/[pluginname]/ajax.php.
    Affected if The ajax.php file is present and the plugin is enabled in the LMS.
  4. Confirm affected parameters are in use
    Review the ajax.php source code and look for the parameters: 'searchActionsToUpdate', 'searchSpecialitiesPending', 'searchSpecialitiesLinked', 'searchUsersToUpdateProfile', 'training_action_data', 'showContinuingTrainingCourses', 'showUsersToEdit'.
    Affected if Any of these parameters are handled by ajax.php without prepared statement usage.
  5. Check if plugin is enabled
    Access the LMS admin panel and verify if the 'Innovación y Cualificación' local plugin is listed as enabled in Site Administration > Plugins > Local plugins.
    Affected if The plugin is installed and enabled.

The environment is affected if the 'Innovación y Cualificación' local administration plugin is installed and enabled, regardless of version, since no fixed version was specified in the advisory.

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

Implement prepared statements/parameterized queries for all listed parameters in ajax.php. If immediate patching is unavailable, disable the affected plugin or restrict access to ajax.php via web server configuration while awaiting an official vendor patch.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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