CVE-2025-25951
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 · uneditedAn information disclosure vulnerability in the component /rest/cb/executeBasicSearch of Serosoft Solutions Pvt Ltd Academia Student Information System (SIS) EagleR v1.0.118 allows attackers to access sensitive user information.
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 confidenceAn information disclosure vulnerability in the /rest/cb/executeBasicSearch REST API endpoint of Academia SIS EagleR v1.0.118 allows unauthenticated or unauthorized attackers to query and retrieve sensitive user information through the search functionality without proper access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= eagler-1.0.118CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm installed Academia SIS EagleR versionCheck the application version through its web interface, About page, or by querying the /rest/cb/version or similar version endpoint. Alternatively, check the deployment artifacts for version metadata.Affected if The installed version is exactly 1.0.118 (eagler-1.0.118)
-
Identify if the REST API endpoint is accessibleAttempt to access the /rest/cb/executeBasicSearch endpoint via HTTP GET or POST request from an unauthenticated browser or curl command.Affected if The endpoint responds with any HTTP status (200, 400, 401, 403) rather than rejecting the request outright at the network or application layer
-
Test authentication enforcement on the endpointSend a request to /rest/cb/executeBasicSearch without any authentication tokens, session cookies, or credentials. Observe whether the server returns user data or a proper authentication error (401 Unauthorized).Affected if The endpoint returns sensitive user information, search results, or any data payload without requiring valid authentication
-
Test authorization controls for unauthorized accessLog in with a low-privilege or unauthorized user account, then query /rest/cb/executeBasicSearch for data belonging to other users or roles. Verify if access controls prevent cross-user data retrieval.Affected if An authenticated but unauthorized user can query and retrieve data they should not have permission to access
Your environment is affected if Academia SIS EagleR version 1.0.118 is installed AND the /rest/cb/executeBasicSearch endpoint is exposed without proper authentication or authorization controls.
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 dataImplement proper authentication and role-based authorization checks on the /rest/cb/executeBasicSearch endpoint to ensure users can only access data they are explicitly authorized to view.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25951 — 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-25951 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