amauric WPMobile.App Plugin up to 11.82 on WordPress wpmobile_auto_mail authorization

Summaryinfo

A vulnerability, which was classified as critical, has been found in amauric WPMobile.App Plugin up to 11.82. Affected by this issue is some unknown functionality. This manipulation of the argument wpmobile_auto_mail causes authorization. The identification of this vulnerability is CVE-2026-94541. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as critical was found in amauric WPMobile.App Plugin up to 11.82. Affected by this vulnerability is an unknown functionality. The manipulation of the argument wpmobile_auto_mail with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The WPMobile.App – Android and iOS App Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 11.82 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to exfiltrate password-reset URLs for arbitrary users, including administrators, mirrored into the push queue by the mail-to-push feature, and use those URLs to take over the targeted accounts. This exploit chain requires the plugin's mail-to-push feature (wpmobile_auto_mail=1) to be enabled, as that setting is what causes outbound WordPress password-reset emails — including the reset URL and key — to be mirrored into the push row queue where they become accessible to the attacker.

The advisory is shared at wordfence.com. This vulnerability is known as CVE-2026-94541 since 09/21/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/02/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• amauric

Name

• WPMobile.App Plugin

Version

• 11.0
• 11.1
• 11.2
• 11.3
• 11.4
• 11.5
• 11.6
• 11.7
• 11.8
• 11.9
• 11.10
• 11.11
• 11.12
• 11.13
• 11.14
• 11.15
• 11.16
• 11.17
• 11.18
• 11.19
• 11.20
• 11.21
• 11.22
• 11.23
• 11.24
• 11.25
• 11.26
• 11.27
• 11.28
• 11.29
• 11.30
• 11.31
• 11.32
• 11.33
• 11.34
• 11.35
• 11.36
• 11.37
• 11.38
• 11.39
• 11.40
• 11.41
• 11.42
• 11.43
• 11.44
• 11.45
• 11.46
• 11.47
• 11.48
• 11.49
• 11.50
• 11.51
• 11.52
• 11.53
• 11.54
• 11.55
• 11.56
• 11.57
• 11.58
• 11.59
• 11.60
• 11.61
• 11.62
• 11.63
• 11.64
• 11.65
• 11.66
• 11.67
• 11.68
• 11.69
• 11.70
• 11.71
• 11.72
• 11.73
• 11.74
• 11.75
• 11.76
• 11.77
• 11.78
• 11.79
• 11.80
• 11.81
• 11.82

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion