CVE-2024-13888

WPMobile.App <= 11.56 - Open Redirect via 'redirect' Parameter

2025-02-19 19:45

Strategic Overview

Status: Patched in 11.57
Affected Plugin: WPMobile.App
Affected Version: <= 11.56
CVSS: 7.2High
Weakness type: CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE: CVE-2024-13888

At a glance

CVE-2024-13888 is a high-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the WPMobile.App WordPress plugin, affecting versions <= 11.56. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 11.57; sites on affected versions should update now. Disclosed February 2025, reported by Krzysztof Zając.

Vulnerability Overview

The WPMobile.App plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 11.56. This is due to insufficient validation on the redirect URL supplied via the 'redirect' parameter. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

WPMobile.App <= 11.56 carries this weakness at redirect, and reaching it takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. For WPMobile.App the fix is 11.57: builds <= 11.56 are affected, anything from 11.57 onward is not.

Remediation

Update to version 11.57, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPMobile.App: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPMobile.App 11.57 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-13888 https://www.wordfence.com/threat-intel/vulnerabilities/id/a139f0fc-f3e0-4759-aa8d-ba138e5ccc87 https://nvd.nist.gov/vuln/detail/CVE-2024-13888

Related records

Other vulnerabilities in WPMobile.App

CVSS Vector

7.2

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/