Academia Student Information SystemApplication · Serosoft

CVE-2025-27583

CRITICAL · 9.1 CVSS v3.1 Published 2025-03-03
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
Incorrect access control in the component /rest/staffResource/findAllUsersAcrossOrg of Serosoft Solutions Pvt Ltd Academia Student Information System (SIS) EagleR v1.0.118 allows create and modify user accounts, including an Administrator account.

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

The Academia SIS EagleR v1.0.118 application contains a broken access control vulnerability in the /rest/staffResource/findAllUsersAcrossOrg REST endpoint. This endpoint allows unauthenticated or unauthorized attackers to create new user accounts and modify existing accounts, including elevating privileges to Administrator level, due to missing or inadequate authorization checks.

MitigationImplement proper role-based access control (RBAC) on the /rest/staffResource/findAllUsersAcrossOrg endpoint to verify user authentication and ensure the requesting user has appropriate administrative privileges before allowing account creation or modification operations.

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
Academia Student Information SystemApplication
Affected:= eagler-1.0.118

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Confirm Academia SIS EagleR installation
    Identify if Serosoft Academia Student Information System is running in your environment by checking for web application files, services, or banner information mentioning 'Academia SIS' or 'EagleR'
    Affected if The application is installed and running
  2. Verify installed version
    Check the application version through the web interface header/footer, API endpoint, configuration files, or server logs for 'eagler-1.0.118'
    Affected if Version is exactly 1.0.118 (eagler-1.0.118)
  3. Test endpoint accessibility
    Send an HTTP GET or POST request to /rest/staffResource/findAllUsersAcrossOrg and observe the response
    Affected if Endpoint returns HTTP 200 or any valid response (not 401/403) without authentication credentials
  4. Verify lack of authorization enforcement
    Attempt to access the endpoint without valid session tokens or credentials and check if the application allows account creation or modification operations
    Affected if Endpoint permits operations without requiring authentication or proper authorization header/token

You are affected if Academia SIS EagleR version 1.0.118 is installed and the /rest/staffResource/findAllUsersAcrossOrg endpoint is accessible without authentication, allowing unauthorized account management operations.

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

Implement proper role-based access control (RBAC) on the /rest/staffResource/findAllUsersAcrossOrg endpoint to verify user authentication and ensure the requesting user has appropriate administrative privileges before allowing account creation or modification operations.

Fix this in Academia Student Information System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-27583 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