dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-28076

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Multiple SQL injection vulnerabilities in EasyVirt DCScope <= 8.6.4 and CO2Scope <= 1.3.4 allows remote authenticated attackers to execute arbitrary SQL commands via the (1) timeago, (2) user, (3) filter, (4) target, (5) p1, (6) p2, (7) p3, (8) p4, (9) p5, (10) p6, (11) p7, (12) p8, (13) p9, (14) p10, (15) p11, (16) p12, (17) p13, (18) p14, (19) p15, (20) p16, (21) p17, (22) p18, (23) p19, or (24) p20 parameter to /api/management/updateihmsettings; the (25) ID, (26) NAME, (27) CPUTHREADNB, (28) RAMCAP, or (29) DISKCAP parameter to /api/capaplan/savetemplates.

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

Multiple SQL injection vulnerabilities in EasyVirt DCScope <= 8.6.4 and CO2Scope <= 1.3.4 allow authenticated remote attackers to execute arbitrary SQL commands via 29 different parameters across two API endpoints (/api/management/updateihmsettings and /api/capaplan/savetemplates). The vulnerabilities stem from unsanitized user input being directly incorporated into SQL queries.

MitigationUpgrade to patched versions if available; otherwise, implement proper input validation and refactor vulnerable queries to use parameterized queries or prepared statements. Apply least-privilege database access controls to limit impact of successful injection.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Identify the installed DCScope version
    Check the product's about page, installation directory, or running service version information for EasyVirt DCScope. Compare against the affected range <= 8.6.4.
    Affected if The installed version is 8.6.4 or lower.
  2. Identify the installed CO2Scope version
    Check the product's about page, installation directory, or running service version information for EasyVirt CO2Scope. Compare against the affected range <= 1.3.4.
    Affected if The installed version is 1.3.4 or lower.
  3. Verify API endpoint exposure
    Check network configuration or web server logs to determine if the endpoints /api/management/updateihmsettings and /api/capaplan/savetemplates are exposed to network users.
    Affected if Either vulnerable endpoint is accessible from untrusted networks without additional filtering.
  4. Assess authentication controls
    Review the application's authentication configuration to confirm whether the vulnerable API endpoints require valid user credentials for access.
    Affected if The API endpoints allow unauthenticated or weakly authenticated access.

The environment is affected if running EasyVirt DCScope <= 8.6.4 or CO2Scope <= 1.3.4 with the vulnerable API endpoints accessible to authenticated attackers.

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

Upgrade to patched versions if available; otherwise, implement proper input validation and refactor vulnerable queries to use parameterized queries or prepared statements. Apply least-privilege database access controls to limit impact of successful injection.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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