Sunbirded PortalApplication · Sunbird

CVE-2025-70028

HIGH · 7.5 CVSS v3.1 Published 2026-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
An issue pertaining to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') was discovered in Sunbird-Ed SunbirdEd-portal v1.13.4.

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

A path traversal vulnerability (CWE-22) exists in SunbirdEd-portal v1.13.4 allowing attackers to access files outside restricted directories through insufficient input validation on file path parameters. This high-severity flaw (CVSS 7.5) could enable unauthorized file system access.

MitigationImplement strict input validation and path sanitization using allowlist approaches; canonicalize paths and verify they remain within intended directories before file operations; restrict file access permissions.

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
Sunbirded PortalApplication
Affected:= 1.13.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 SunbirdEd-portal version
    Check the installed package version by reviewing package.json, or run 'npm list @project-sunbird/sunbirded-portal' or 'npm list sunbirded' in the application directory
    Affected if The installed version is exactly 1.13.4
  2. Verify file path parameter handling is active
    Review application logs or configuration to confirm whether file upload, download, or path-based API endpoints are enabled and accessible
    Affected if File path parameter endpoints are exposed and processing user-supplied paths without additional validation layers
  3. Inspect input validation for path parameters
    Examine application code or middleware configurations that handle file path inputs, looking for validation logic on path-related request parameters
    Affected if No explicit allowlist validation or path canonicalization is performed on file path parameters before use
  4. Check for path traversal protection
    Review proxy configurations, web server settings, or application firewall rules that may inspect path traversal sequences (such as ../) in requests
    Affected if No path traversal protection mechanisms are in place to block or sanitize sequences like ../ in file path inputs

You are affected if SunbirdEd-portal version 1.13.4 is running and file path parameter handling is enabled without proper input validation or path traversal protection.

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 strict input validation and path sanitization using allowlist approaches; canonicalize paths and verify they remain within intended directories before file operations; restrict file access permissions.

Fix this in Sunbirded Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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