# CVE-2025-70027: Server-side request forgery in n/a

> Attackers can exploit Server-Side Request Forgery in SunbirdEd portal to obtain sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-vvv2-p9hv-8634

## What is CVE-2025-70027?

CVE-2025-70027 is a high-severity server-side request forgery vulnerability in n/a, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue pertaining to CWE-918: Server-Side Request Forgery was discovered in Sunbird-Ed SunbirdEd-portal v1.13.4. This allows attackers to obtain sensitive information

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-70027?

It affects 1 product.


Products: Sunbird Sunbirded-Portal.

## How do I fix CVE-2025-70027?

No fix has been published for CVE-2025-70027 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-70027 being exploited?

There is no known exploitation of CVE-2025-70027 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-70031](https://insights.sbomify.com/CVE-2025-70031/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2025-70028](https://insights.sbomify.com/CVE-2025-70028/): Path traversal in n/a (high 7.5)
- [CVE-2025-70030](https://insights.sbomify.com/CVE-2025-70030/): Denial of service in n/a (high 7.5)
- [CVE-2025-70029](https://insights.sbomify.com/CVE-2025-70029/): An issue in Sunbird-Ed SunbirdEd-portal v1.13.4 allows attackers to obtain sensitive information. (high 7.5)
- [CVE-2025-70032](https://insights.sbomify.com/CVE-2025-70032/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70027 and fix it if it is affected.

What it is: CVE-2025-70027 is a high-severity server-side request forgery vulnerability in n/a, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70027 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70027/ (Markdown: https://insights.sbomify.com/CVE-2025-70027/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70027
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70027
- OSV: https://osv.dev/vulnerability/CVE-2025-70027

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70027/
Summaries are generated and may contain mistakes; the official description above is the record.
