Skip to content


Repository files navigation


This repository contains a way to run code inside the Wii U's web browser. It provides a means to execute arbitrary code in the Cafe OS userspace on the Espresso processor. Also included is a Cafe OS kernel exploit, which runs in the Espresso's user-mode. The exploits in this repository do not provide any access to IOSU on the Starbuck. We hope to implement this in the future, but the exploit is currently limited to Espresso only.

Right now, almost all firmware versions are compatible:

  • Firmware versions 2.0.0 (first instalment of the Internet Browser) to 5.1.0 are supported by exploiting an use-after-free bug (CVE-2013-2842).
  • Firmware version 5.3.2 is supported by exploiting a memory corruption bug (CVE-2014-1300).
  • Firmware versions 5.1.1 to 5.3.1 are also supported, but currently unimplemented.
  • Firmware version 5.4.0 is supported.
  • Firmware version 5.5.0/5.5.1 are supported, but only userland.

What's inside?

Inside this repository, you will find a set of tools that allow you to compile your own C code and embed it inside a webpage to be executed on the Wii U. There are also a few code examples doing certain tasks on the Wii U. Most notably, there is a Cafe OS kernel exploit, and an RPC client which allows your Wii U to execute commands sent over the network from a Python script. Nothing in this repository is useful to the general public. You will only find it useful if you are a C programmer and want to explore the system by yourself.

How do I use this?

C build system

This repository contains a C build system, which allows you to compile your own C code and embed it inside a webpage to be executed on the Wii U. The webpage contains some Javascript code that triggers the WebKit bug and passes control to your C code. Running your own C code on the Wii U gives you full access to the SDK libraries. Any function's address can be retrieved if you know its symbol name and containing library's name (more on this below). Before using the C build system, you must have the following tools:

  • Unix-like shell environment (use Cygwin to get this on Windows)
  • devkitPPC (needed to compile and link the C code), with C:\devkitPro\devkitPPC\bin added to PATH
  • Python 3.x (must add C:\Python34 to PATH) or 2.x

Build Example

The osscreenexamples folder contains projects using OSScreen and the loader.c from libwiiu. The examples folder does not use OSScreen and uses the loader.c in the projects local directory.

  • python <project path>
  • python osscreenexamples/template

If you want to build for 5.4.0,run any makefile of any folder,and use the code532.bin with Browserhax (which needs this)

If you want to build for 5.5.0/5.5.1, you first have to compile libwiiu for 5.5.0/5.5.1. For that you go into libwiiu and run make. Now you can go into the osscreenexamples or examples folder and run one of the makefiles. The now compiled code550.bin in the bin folder can be used with Browserhax (which needs this). Please note that not all examples may work with 5.5.0/5.5.1.

Accessing the SDK libraries

Programming the Wii U is built around the SDK libraries: a set of useful functions that provide access to graphics, audio, input, filesystem, and network functions. They are accessible from any application, including the web browser, which means that code running inside it using an exploit also gets access. All SDK libraries let you get the address of any contained function by its library and symbol name.

Every SDK library is an RPL file, a modification of the ELF format. For example, gx2.rpl is the name of the graphics library, vpad.rpl is the name of the Gamepad input library, and nsysnet.rpl is the name of the BSD sockets library. There is also a special RPL called coreinit.rpl, which provides direct access to many core Cafe OS services, including memory management and threading.

As mentioned, it is possible to get symbol addresses from SDK libraries dynamically. This is done through the coreinit OSDynLoad functions. You can access these functions by including coreinit.h in your C file.

There are two functions involved in getting a symbol. The first function is OSDynLoad_Acquire(), which loads the RPL you specify. OSDynLoad_Acquire() takes two arguments: the RPL name and a pointer to an integer handle. It can also be used to get a handle to a library that's already loaded. The second function is OSDynLoad_FindExport(), which finds a symbol given a library handle. It takes four arguments: the integer handle returned by OSDynLoad_Acquire(), whether the symbol is data or not (usually not), the symbol name, and a pointer to where the symbol address should be stored. Here are the function prototypes:

  • void OSDynLoad_Acquire(char \*rplname, unsigned int \*handle);
  • void OSDynLoad_FindExport(unsigned int handle, int isdata, char \*symname, void \*address);

For example, let's say I wanted the VPADRead() symbol from vpad.rpl. If I have an integer called handle, I first call OSDynLoad_Acquire("vpad.rpl", &handle); to get a handle to the RPL. Next, if I have a function pointer I want to put the symbol address in, called VPADRead, I call OSDynLoad_FindExport(handle, 0, "VPADRead", &VPADRead); to retrive VPADRead()'s address. For more samples of this, look at almost any libwiiu code example.

RPC system

In addition to letting you write your own C code to run on the Wii U, this repository also includes an RPC system to interactively experiment with the Wii U. It allows you to send commands over the network for your Wii U to execute. The two components of the RPC system are the server, a C program running on the Wii U listening for commands, and the client, a Python script that sends the commands.

To use the RPC system, first ensure that your PC and Wii U are connected to the same network. Once they are, find out your PC's IP address using the ipconfig command (Windows) or ifconfig command (Linux and OS X). Modify PC_IP in socket.h to be your PC's IP address (rather than, which it currently is). Build rpc.c and it will go in your htdocs.

Next, start in an interactive Python session (IDLE or IPython is a good choice). Once you've started, navigate to the browser exploit you just made on your Wii U. It should appear to finish loading the page, and the UI will continue to be responsive, but web browsing will be disabled. At that point, the Python shell should say something along the lines of "Connected by" followed by your Wii U's IP. Now you can control your Wii U with these commands:

  • rpc.read32(address, num_words) - Read num_words words starting at address, returning a list of words
  • rpc.write32(address, words) - Write each word in the list words to memory starting at address
  • rpc.dump_mem(address, length, filename) - Dump length bytes from memory starting at address to filename
  • symbol(rplname, symname) - Get the symbol symname from RPL rplname and turn it into a callable Python function
  • rpc.exit() - Exit the browser and go back to the menu


  • Marionumber1
  • TheKit
  • Hykem
  • comex
  • Chadderz
  • Relys
  • NWPlayer123
  • Mathew_Wi