dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-2200

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 IcProgreso Innovación y Cualificación plugin. This vulnerability allows an attacker to obtain, update and delete data from the database by injecting an SQL query on the parameters user, id, idGroup, start_date and end_date in the endpoint /report/icprogreso/generar_blocks.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 · high confidence

SQL injection vulnerability in the IcProgreso plugin's generar_blocks.php endpoint allows attackers to inject malicious SQL through multiple parameters (user, id, idGroup, start_date, end_date). With a CVSS of 9.3, this critical flaw enables unauthenticated attackers to read, modify, or delete arbitrary database content.

MitigationImmediately disable or restrict access to the affected endpoint until a vendor patch is available; implement parameterized queries (prepared statements) for all database operations and apply input validation on all user-supplied parameters.

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. Locate the IcProgreso plugin installation
    Search the web server document root for directories named 'icprogreso', 'IcProgreso', or similar case variations. Common paths: /wp-content/plugins/, /plugins/, or application-specific plugin folders.
    Affected if The IcProgreso plugin directory exists on the server
  2. Identify the vulnerable PHP file
    Check for the presence of /report/icprogreso/generar_blocks.php within the plugin or application directory structure. Use file system search: find /path/to/webroot -name 'generar_blocks.php' 2>/dev/null
    Affected if The file generar_blocks.php exists in the expected path
  3. Verify the endpoint is web-accessible
    Attempt a GET request to the full URL of the endpoint (e.g., https://yourdomain.com/report/icprogreso/generar_blocks.php). Check HTTP response status and content.
    Affected if The endpoint returns an HTTP 200 or other valid response rather than 404/403, indicating the file is reachable
  4. Inspect the source code for vulnerable parameters
    Open generar_blocks.php and search for direct use of $_GET or $_REQUEST for parameters: user, id, idGroup, start_date, end_date. Look for concatenated SQL queries without prepared statements.
    Affected if The code contains unsanitized SQL queries using the five listed parameters (user, id, idGroup, start_date, end_date)
  5. Test parameter acceptance
    Send a request with benign test values to each parameter (e.g., ?user=test&id=1&idGroup=1&start_date=2024-01-01&end_date=2024-12-31). Observe if the application processes these without error or validation.
    Affected if The application accepts and processes the parameters without rejecting or sanitizing the input

If the IcProgreso plugin is installed with the generar_blocks.php endpoint accessible and the source code shows direct SQL parameter usage, the environment is likely affected.

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

Immediately disable or restrict access to the affected endpoint until a vendor patch is available; implement parameterized queries (prepared statements) for all database operations and apply input validation on all user-supplied parameters.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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