External risk intelligence

Mstoreapp WordPress Plugin Session Hijacking Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-11127

The vulnerability affects WordPress plugins designed to provide mobile app and multivendor functionality. These plugins are typically installed on web servers to expose public-facing APIs and interfaces that facilitate e-commerce and user interaction, making them commonly reachable via the internet as part of the application's standard operation.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability impacts Mstoreapp mobile app and multivendor plugins for WordPress. It allows unauthenticated users to potentially gain session access to any user's account if their email address is known, posing a significant risk to user data and system integrity.

  • Unauthenticated access to user accounts via email.
  • High impact on user privacy and system security.
  • Confirm relevance and understand potential exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this vulnerability by knowing a target user's email address. They can then send a request to the application's AJAX endpoint, which fails to properly verify the user's identity. This allows the attacker to obtain a valid session token for any user, potentially leading to full account takeover and unauthorized actions.

  • No authentication required.
  • AJAX action allows session retrieval.
  • Full account takeover risk.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated users to obtain valid sessions for other users when they know the target's email address. This access could potentially affect system data, user data, service behavior, or sensitive information if the application handles such data in ways that are not protected from session hijacking.

  • User session data at risk.
  • Unauthenticated access via email.
  • Compromise of user accounts.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership

This vulnerability impacts WordPress plugins used for mobile app and multivendor functionalities, suggesting that application owners and platform teams are the primary stakeholders for remediation. The initial focus should be on identifying all instances of the affected plugins, assessing their exposure and business criticality, and confirming ownership before planning remediation efforts.

  • Application owners should manage the issue.
  • Verify plugin reachability and business criticality first.
  • Plan remediation based on confirmed risk and ownership.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Mstoreapp Mobile App and Multivendor plugin?

These are WordPress plugins that extend a site's functionality to support mobile applications and multi-vendor e-commerce marketplaces. They create a bridge between your WordPress database and external mobile interfaces, managing user sessions and transactions to ensure the mobile experience mirrors the website's core capabilities.

What does CVE-2025-11127 mean for site security?

This CVE describes a failure in identity verification during AJAX processes. Essentially, the software lacks a proper gatekeeper when handling requests for session data. Because the plugin does not confirm who is making the request, an external actor can impersonate any registered user simply by providing their email address.

How does an attacker trigger this vulnerability?

An attacker targets specific AJAX endpoints exposed by the plugins. The flaw is triggered by sending a crafted request containing a known target email address. Note that this does not require a password or an existing active session from the attacker; the vulnerability exists because the system trusts the provided email input implicitly rather than requiring authenticated proof of identity.

Is my site at risk according to Halo Surface Signal?

Because these plugins are designed to support mobile and multi-vendor features, they typically expose public-facing APIs to function correctly. Halo Surface Signal identifies these as likely reachable over the internet, meaning your site is in the high-risk category for external access if you have these specific plugin versions installed.

What should I do if I use these plugins?

Begin by auditing your WordPress environment to confirm which specific plugins and versions are active. Once you have identified all instances, determine the business criticality of those sites. Prioritize checking for available updates from the developer or implementing temporary restrictions on the affected AJAX endpoints until a secure patch is verified and deployed.

References