# CVE-2024-4989: Open Redirection via Callback URL in WSO2 API Manager Allows Phishing Attacks


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-xghc-f7xh-fw48

## What is CVE-2024-4989?

CVE-2024-4989 is a medium-severity vulnerability in WSO2 API Manager, published on 21 Oct 2026. 

### Official description

The callback URL parameter in WSO2 API Manager fails to validate user-supplied input, allowing it to be controlled by malicious actors.

Exploitation of this vulnerability could lead to users being redirected to attacker-controlled web pages. This can be used in conjunction with social engineering techniques to trick users into interacting with malicious links, potentially resulting in phishing attacks aimed at acquiring sensitive information or causing other harm.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2024-4989 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4989 is a medium-severity vulnerability in WSO2 API Manager, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2024-4989 in the wild and no public exploit code.

Affected product: WSO2 API Manager. 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-4989/ (Markdown: https://insights.sbomify.com/CVE-2024-4989/index.md)
```

## Sources

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

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