CVE-2025-25953
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 · uneditedSerosoft Solutions Pvt Ltd Academia Student Information System (SIS) EagleR v1.0.118 was discovered to contain an Azure JWT access token exposure. This vulnerability allows authenticated attackers to escalate privileges and access sensitive 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 · moderate confidenceThe Academia Student Information System (SIS) EagleR v1.0.118 contains an Azure JWT access token exposure vulnerability. Authenticated attackers can obtain exposed JWT tokens to escalate privileges and access sensitive information within the system.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Verify Academia SIS EagleR versionCheck installed software version of Serosoft Academia Student Information System (EagleR). If running in Azure, query the deployed application version or check application manifest/config file for version identifier.Affected if Version is exactly 1.0.118 (eagler-1.0.118)
-
Audit application logs for JWT token leakageSearch application log files, debug logs, and audit trails for patterns resembling JWT tokens (header.payload.signature format). Use regex or string search for 'eyJ' prefix commonly found in JWT tokens.Affected if Any Azure JWT access tokens are found logged in plaintext
-
Inspect database or storage for exposed tokensExamine database tables, temporary files, cache directories, or configuration storage used by the application for any stored JWT tokens. Check for tokens stored in plaintext rather than hashed or encrypted.Affected if JWT tokens are found stored insecurely in plaintext
-
Review HTTP traffic and API responsesCapture and inspect HTTP responses from the application, particularly during authentication flows. Check response bodies, headers, and error messages for exposed JWT tokens being returned to clients.Affected if JWT tokens appear in HTTP responses where they should not be visible
Environment is affected if Academia SIS EagleR version 1.0.118 is deployed AND any JWT tokens are found exposed in logs, storage, or network traffic.
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 dataIdentify and remediate the source of JWT token exposure (likely insecure storage, logging, or transmission), rotate all exposed Azure JWT tokens immediately, and implement proper secrets management to prevent future token leakage.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25953 — 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-25953 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