# CVE-2024-48590: Server-side request forgery in n/a

> An attacker can exploit SSRF in SpiraTeam to escalate privileges and access sensitive information.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-pvrp-6fjq-x9rj

## What is CVE-2024-48590?

CVE-2024-48590 is a critical server-side request forgery vulnerability in n/a, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Inflectra SpiraTeam 7.2.00 is vulnerable to Server-Side Request Forgery (SSRF) via the NewsReaderService. This allows an attacker to escalate privileges and obtain sensitive information.

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

## Which versions are affected by CVE-2024-48590?

It affects 1 product.


Products: Inflectra Spirateam.

## How do I fix CVE-2024-48590?

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

## Is CVE-2024-48590 being exploited?

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

Public exploit code:

- https://github.com/GCatt-AS/CVE-2024-48590 (github_poc): https://github.com/GCatt-AS/CVE-2024-48590

## Other vulnerabilities in n/a

- [CVE-2024-48591](https://insights.sbomify.com/CVE-2024-48591/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48590 and fix it if it is affected.

What it is: CVE-2024-48590 is a critical server-side request forgery vulnerability in n/a, published on 20 Mar 2025. 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-2024-48590 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-2024-48590/ (Markdown: https://insights.sbomify.com/CVE-2024-48590/index.md)
```

## Sources

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

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