CAPEC-500

How the attack unfolds

1. Explore

   The attacker looks for a way in.

   1. [Determine target web application] An adversary first needs to determine what web application they wish to target.

      2 techniques

      • Target web applications that require users to enter sensitive information.
      • Target web applications that an adversary wishes to operate on behalf of a logged in user.

2. Experiment

   They probe what they found.

   2. [Create malicious application] An adversary creates an application, often mobile, that incorporates a WebView component to display the targeted web application. This malicious application needs to downloaded by a user, so adversaries will make this application useful in some way.

      2 techniques

      • Create a 3rd party application that adds useful functionality to the targeted web application. Victims will download the application as a means of using the targeted web application.
      • Create a fun game that at some point directs a user to the targeted web application. For example, prompt the user to buy in game currency by directing them to PayPal.

   3. [Get the victim to download and run the application] An adversary needs to get the victim to willingly download and run the application.

      2 techniques

      • Pay for App Store advertisements
      • Promote the application on social media, either through accounts made by the adversary or by paying for other accounts to advertise.

3. Exploit

   They carry out the attack.

   4. [Inject malicious code] Once the victim runs the malicious application and views the targeted web page in the WebView component, the malicious application will inject malicious JavaScript code into the web application. This is done by using WebView's loadURL() API, which can inject arbitrary JavaScript code into pages loaded by the WebView component with the same privileges. This is often done by adding a script tag to the document body with a src destination to a remote location that serves malicious JavaScript code.

      3 techniques

      • Execute operations on the targeted web page on behalf of an authenticated user.
      • Steal cookie information from the victim.
      • Add in extra fields to the DOM in an attempt to get a user to divulge sensitive information.

Prerequisites

• An adversary must be able install a purpose built malicious application onto the device and convince the user to execute it. The malicious application is designed to target a specific web application and is used to load the target web pages via the WebView component. For example, an adversary may develop an application that interacts with Facebook via WebView and adds a new feature that a user desires. The user would install this 3rd party app instead of the Facebook app.

Mitigations

• The only known mitigation to this type of attack is to keep the malicious application off the system. There is nothing that can be done to the target application to protect itself from a malicious application that has been installed and executed.

Weaknesses it exploits

• CWE-749 Exposed Dangerous Method or Function
• CWE-940 Improper Verification of Source of a Communication Channel

Recent CVEs with these weaknesses

1. 5.5CVE-2026-1074052026-11-10

   An exposed dangerous function in Ivanti EPMM before version 12.10.0.1, 12.9.0.3, and 12.8.0.5 allows a local authenticated attacker to trigger a denial of service.

2. 9.9CVE-2026-769652026-11-10

   SAP NetWeaver Application Server ABAP and ABAP Platform does not perform necessary authorization checks for certain internal functionality. An attacker with low privileges could invoke affected functionality to execute arbitrary operating …

3. 9.3CVE-2026-1133632026-11-09

   Improper Input Validation in the network communication processing in NEC Corporation WebSAM WinShare Ver 7.2.0 through 7.5.0, Ver 7.6.0 and Ver 7.7.0 through 7.7.2 on Windows allows a remote unauthenticated attacker to execute arbitrary co…

4. 9.8CVE-2026-1167792026-11-05

   FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.3, sofia_presence_handle_sip_i_message() s…

5. 8.3CVE-2026-927042026-11-04

   SharpEmu is an experimental PlayStation 5 emulator for Windows and Linux. In version 0.0.3-release.3 and earlier, the repository-provided debugger frontend tooling is vulnerable while running. This tooling is not included in the release ar…

6. 7.1CVE-2026-1211452026-11-04

   This vulnerability exists in the iRA 2.0 and iRA.ev mobile applications due to insufficient validation of URLs and origins loaded within the WebView component. A remote attacker could exploit this vulnerability by sending malicious web con…

7. 3.1CVE-2026-768942026-11-03

   CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, the DataStore table UI in src/resources/datastore-table-ui.ts accepts window message events without validating event.origin and sends JSON-RPC messages throug…

8. 7.4CVE-2026-442652026-11-03

   Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, Elo's programmatic AST API accepts arbitrary values from JSON-deserialized input, plugin output, or other untyped sources and interpolates them into generate…

The newest records naming one of them. Each weakness's page lists them all.

Related attack patterns

Part of

• CAPEC-253 Remote Code Inclusion

MITRE's words, unchanged: CAPEC-500 at MITRE. CAPEC is Copyright © 2007–2026, The MITRE Corporation, used under the CAPEC terms of use: “The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use Common Attack Pattern Enumeration and Classification (CAPEC™) for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE’s copyright designation and this license in any such copy.” CAPEC and the CAPEC logo are trademarks of The MITRE Corporation. Credits. All attack patterns.