CVE-2026-103421 amauric CVE debrief

Who should care

Defenders responsible for WordPress installations using the WPMobile.App plugin should assess exposure and prioritize verification of the plugin's configuration and version. This includes reviewing the plugin's settings to ensure the content mode is not set to 'webview' unless necessary, and verifying that the plugin is up-to-date to prevent potential exploitation.

Why it matters

The WPMobile.App plugin for WordPress is vulnerable to Stored Cross-Site Scripting, allowing unauthenticated attackers to inject arbitrary web scripts. Defenders should prioritize verifying the plugin's configuration and version to prevent potential exploitation.

• Unauthenticated attackers could inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
• The vulnerability requires the app's content mode to be configured as 'webview' (i.e., the 'speed' option is not set to '1').
• Defenders should verify the configuration of the WPMobile.App plugin to ensure the content mode is not set to 'webview' unless necessary.
• Remediation priority follows from verifying the plugin's version to ensure it is up-to-date.

Technical summary

The WPMobile.App – Android and iOS App Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'REQUEST_URI (path segment after /android_json/search/)' parameter in all versions up to, and including, 11.84 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Defensive priority

Defenders should prioritize verifying the configuration of the WPMobile.App plugin, particularly ensuring that the content mode is not set to 'webview' unless necessary, and review the plugin's version to ensure it is up-to-date.

Recommended defensive actions

• Verify the configuration of the WPMobile.App plugin to ensure the content mode is not set to 'webview' unless necessary.
• Review the plugin's version to ensure it is up-to-date.
• Monitor for potential exploitation attempts targeting the vulnerable parameter.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.