Skip to main content
Vulnerability Database/CVE-2024-43933

CVE-2024-43933: WPMobile.App Stored XSS Vulnerability

CVE-2024-43933 is a stored cross-site scripting flaw in WPMobile.App wpappninja that enables attackers to inject malicious scripts. This post explains its impact, affected versions up to 11.48, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-43933 Overview

CVE-2024-43933 is a stored Cross-Site Scripting (XSS) vulnerability [CWE-79] affecting the Amauri WPMobile.App WordPress plugin (wpappninja). The flaw results from improper neutralization of input during web page generation and allows attackers to inject persistent malicious scripts into pages served to administrators and site visitors. The vulnerability affects all plugin versions up to and including 11.48. Successful exploitation requires user interaction, such as viewing a page containing the stored payload. The issue is tracked in the Patchstack vulnerability database and published by the WordPress security ecosystem.

Critical Impact

Attackers can store malicious JavaScript that executes in victim browsers, enabling session theft, account takeover of administrators, and arbitrary actions within the WordPress site context.

Affected Products

  • Amauri WPMobile.App (plugin slug: wpappninja)
  • All versions from n/a through 11.48
  • WordPress sites running the vulnerable plugin as an Android/iOS mobile application bridge

Discovery Timeline

  • 2024-10-31 - CVE-2024-43933 published to the National Vulnerability Database
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-43933

Vulnerability Analysis

The vulnerability is a stored XSS flaw in the WPMobile.App plugin for WordPress. The plugin fails to properly sanitize and escape user-supplied input before persisting it and rendering it back inside generated HTML. An attacker who can submit input through an affected plugin field persists a JavaScript payload in the WordPress database. The payload executes each time a user loads the affected page in the browser.

Stored XSS in a WordPress plugin typically enables theft of authentication cookies, forced actions through the WordPress REST API, and injection of secondary malware or redirect chains. Because the payload persists server-side, every visitor to the affected page becomes a potential victim without further attacker interaction.

Root Cause

The root cause is missing or insufficient output encoding of attacker-controlled input within the plugin's page generation logic. WordPress provides escaping primitives such as esc_html(), esc_attr(), and wp_kses_post(), but the vulnerable code paths through version 11.48 do not apply them consistently. This matches the pattern described by CWE-79, Improper Neutralization of Input During Web Page Generation.

Attack Vector

Exploitation occurs over the network and requires user interaction. An attacker with permission to submit data through the plugin interface stores a crafted script payload. When an administrator or visitor subsequently loads the page that renders this data, the browser executes the attacker's JavaScript in the site's origin context. The scope is unchanged, and the impact is limited to integrity, consistent with a reflected or stored script execution scenario on a single-origin WordPress application.

No verified public exploit code is available. Refer to the Patchstack WordPress Plugin Advisory for technical details.

Detection Methods for CVE-2024-43933

Indicators of Compromise

  • Unexpected <script>, onerror, or onload attribute values stored in plugin-related WordPress database tables (wp_options, wp_postmeta).
  • Outbound browser requests from WordPress administrators to unfamiliar domains after loading plugin-managed pages.
  • Creation of new WordPress administrator accounts or modifications to user roles that correlate with admin sessions viewing affected pages.

Detection Strategies

  • Inspect plugin configuration fields and stored post content for HTML or JavaScript syntax that should not exist in normal plugin usage.
  • Enable and review WordPress audit logging around plugin option updates performed by low-privilege accounts.
  • Deploy a Content Security Policy (CSP) in report-only mode and monitor violation reports for inline script execution originating from plugin pages.

Monitoring Recommendations

  • Alert on administrator session cookies accessed by scripts loaded from the WPMobile.App plugin paths.
  • Monitor web server logs for POST requests to plugin endpoints that contain encoded script fragments such as %3Cscript%3E or javascript:.
  • Track plugin version inventory across WordPress deployments and alert on any instance still running wpappninja version 11.48 or earlier.

How to Mitigate CVE-2024-43933

Immediate Actions Required

  • Identify every WordPress site running the WPMobile.App plugin and confirm the installed version.
  • Update the plugin to a release later than 11.48 as published by the vendor, or deactivate and remove the plugin if no fixed version is available.
  • Review stored plugin content and database values for injected script payloads and remove any that are found.
  • Rotate WordPress administrator credentials and invalidate active sessions if signs of exploitation are present.

Patch Information

According to the Patchstack WordPress Plugin Advisory, the vulnerability affects WPMobile.App through version 11.48. Site operators should install the latest vendor release that explicitly addresses CVE-2024-43933 and verify the fix is applied through the WordPress plugin interface.

Workarounds

  • Restrict access to the WordPress administrative interface by IP allowlist until the plugin is updated or removed.
  • Deploy a web application firewall (WAF) rule that blocks requests containing script tags or JavaScript event handlers targeting the plugin endpoints.
  • Enforce a strict Content Security Policy that disallows inline scripts and limits script sources to trusted origins.
  • Limit the number of accounts with permission to edit plugin content to reduce the attacker population.
bash
# Example: WP-CLI commands to inventory and deactivate the vulnerable plugin
wp plugin list --name=wpappninja --fields=name,status,version
wp plugin deactivate wpappninja
wp plugin update wpappninja

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.