dbcve.org
InjectionWeakness · CWE-74

CVE-2025-2351

HIGH · 7.3 CVSS v3.1 Published 2025-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A vulnerability classified as critical was found in DayCloud StudentManage 1.0. This vulnerability affects unknown code of the file /admin/adminScoreUrl of the component Login Endpoint. The manipulation of the argument query leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. 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 DayCloud StudentManage 1.0's login endpoint (/admin/adminScoreUrl) allows remote attackers to inject malicious SQL commands via the 'query' parameter. The lack of input sanitization on this parameter enables database manipulation.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements, implement strict input validation on all user-controlled parameters, and deploy a WAF as a compensating control until the code fix is deployed.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DayCloud StudentManage is installed
    Identify the application by reviewing your web server's deployed applications or checking the application banner. Look for 'DayCloud StudentManage' in the application name or title.
    Affected if The application is DayCloud StudentManage
  2. Verify the application version
    Check the installed version of DayCloud StudentManage through the admin interface, version file, or application metadata. Compare against version 1.0.
    Affected if The version is 1.0 or falls within the 1.x range
  3. Confirm the /admin/adminScoreUrl endpoint exists
    Access the URL path /admin/adminScoreUrl on your server to verify the endpoint is present and reachable.
    Affected if The endpoint returns a valid response (200 OK or similar) rather than a 404 error
  4. Test if the query parameter accepts input
    Send a request to /admin/adminScoreUrl with a test value in the 'query' parameter (for example: ?query=test) and observe if the application processes it without rejecting or sanitizing the input.
    Affected if The application accepts the query parameter without strict input validation or returns SQL-related errors indicating unsanitized input is processed

You are affected if DayCloud StudentManage version 1.0 is running and the /admin/adminScoreUrl endpoint is accessible with an unsanitized 'query' parameter.

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

Replace dynamic SQL queries with parameterized queries or prepared statements, implement strict input validation on all user-controlled parameters, and deploy a WAF as a compensating control until the code fix is deployed.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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