dbcve.org
Api ManagerApplication · Wso2

CVE-2024-1440

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 open redirection vulnerability exists in multiple WSO2 products due to improper validation of the multi-option URL in the authentication endpoint when multi-option authentication is enabled. A malicious actor can craft a valid link that redirects users to an attacker-controlled site. By exploiting this vulnerability, an attacker may trick users into visiting a malicious page, enabling phishing attacks to harvest sensitive information or perform other harmful actions.

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

This is an open redirection vulnerability in multiple WSO2 products affecting the authentication endpoint. When multi-option authentication is enabled, the multi-option URL parameter is not properly validated, allowing attackers to craft malicious links that redirect authenticated users to attacker-controlled websites. This enables phishing attacks where users believe they are visiting a legitimate WSO2-hosted page.

MitigationApply the vendor-provided security patch or upgrade to a fixed WSO2 product version. If immediate patching is not possible, consider disabling multi-option authentication or implementing strict URL validation/whitelisting for redirect URLs in the authentication flow.

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
Api ManagerApplication
Affected:= 3.1.0= 3.2.0= 4.0.0
Identity ServerApplication
Affected:= 5.10.0= 5.11.0= 6.0.0= 6.1.0= 7.0.0
Identity Server As Key ManagerApplication
Affected:= 5.10.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Identify installed WSO2 product and version
    Check the product version by inspecting the product.xml or version.txt file in the WSO2 installation directory, or by logging into the management console and viewing the About section. Common paths: <installation>/bin/wso2server.sh --version or check <installation>/repository/components/plugins for product jar files.
    Affected if The installed version matches 3.1.0, 3.2.0, or 4.0.0 for API Manager; 5.10.0, 5.11.0, 6.0.0, 6.1.0, or 7.0.0 for Identity Server; or 5.10.0 for Identity Server As Key Manager.
  2. Determine if multi-option authentication is enabled
    Examine the authentication configuration file. For older versions, check <installation>/repository/conf/identity/application-authentication.xml. For newer versions using the management console, navigate to Login > Multi Option Authentication or check the deployment.toml file for authentication configurations.
    Affected if Multi-option authentication is enabled in the authentication configuration.
  3. Verify authentication endpoint redirect configuration
    Inspect the authentication endpoint configuration files in <installation>/repository/deployment/server/webapp/authenticationendpoint/ or check the application-authentication.xml for redirect parameters. Look for the multi-option parameter handling in the authentication flow.
    Affected if The authentication endpoint allows arbitrary URL redirection through the multi-option parameter without strict whitelist validation.
  4. Check for URL validation in authentication flow
    Review the application-authentication.xml or equivalent configuration for AllowedURLs, URLValidation, or similar redirect whitelist settings. Look for patterns like <Parameter name="AllowedURLs"> or redirect validation rules.
    Affected if No strict URL whitelist or validation is configured for redirect URLs in the authentication flow, or the multi-option parameter is not explicitly validated.

You are affected if you are running one of the listed WSO2 product versions AND have multi-option authentication enabled without proper URL validation on the authentication endpoint redirect parameter.

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

Apply the vendor-provided security patch or upgrade to a fixed WSO2 product version. If immediate patching is not possible, consider disabling multi-option authentication or implementing strict URL validation/whitelisting for redirect URLs in the authentication flow.

Fix this in Api Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-1440 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