Skip to main content

🎉    We recently published 3 CVE's


Stored cross-site scripting (XSS) in the embedded webserver of AKCP sensorProbe before SP480-20210624 enables remote authenticated attackers to introduce arbitrary JavaScript via the Sensor Description, Email (from/to/cc), System Name, and System Location fields.


Stored cross-site scripting (XSS) in the embedded webserver of certain HP OfficeJet Printers—including the 4630 e-All-in-One Printer and 7110 Wide Format ePrinter— enables remote unauthenticated attackers to introduce arbitrary JavaScript via the printer name and printer location fields. Stored Cross-Site Scripting

In May, independent security researcher Tyler Butler disclosed a series of vulnerabilities in including stored XSS, authentication bypass, and user spoofing.

Executive Overview

In May 2021, independent security researcher Tyler Butler found several critical vulnerabilities in, a popular open-source typing-test application with a booming community of over 100k daily unique visitors. The vulnerabilities included stored cross-site scripting and user impersonation in the tribe chat room feature, as well as an authentication bypass vulnerability enabling any user to set arbitrary test scores and jump to the top of the leaderboard. Tyler engaged the site developer on discord and github, ultimately confirming all vulnearbilities were triaged. The developer was an excpetional partner in addressing the concerns, and even accepted a pull request to add a security policy and security.txt file to further support future security researchers to disclosure issues responsibly.


About the Vendor

Monkeytype is a popular typing-test application with a growing online community. Started in early 2020, it’s quickly become one of the top typing test applications, boasting over 40 million page views. In late May, the lead developer announced some pretty impressive statistics for the site,

  • 100k daily unique visitors
  • 228k registered accounts
  • 139 million started tests
  • 54 million completed tests
  • 2.22 billion seconds which is around 70 years of typing is the beta release for monkeytype’s tribe—a feature which allows users to join rooms, chat, and compete in typing challenges together.

Coordinated Disclosures

The following section details each vulnerability found includnig a proof of concept, statement addressing impact, and mitigation steps taken by the application developer.

Stored Cross-Site Scripting via Tribe Chat

Vulnerability: The monkeytype Tribe Chat is vulnerable to stored cross-site scripting via the (1) message and (2) name parameters. While client side validation as implemented, it fell short of protecting malicious payloads that were injected directly in modified socket requests. To be exploited, a malicious user could create or join a chat room, send a normal message, intercepted the socket request and inject a payload into the name or message fields.

Disclosure Method: According to the bug report policy at the time of discovery, I engaged the application developer on Discord Chat (also here) and opened a Github Issue.

Proof of Concept:

  • Configure BurpSuite to intercept browser traffic
  • Navigate to
  • Click on “create room”
  • Turn on BurpSuite proxy interception
  • Enter a new chat string
  • Intercept the web socket traffic, and change the chat string to an XSS payload, example below.
  • Stop intercepting traffic, browse the chat room. The payload will execute. In this example, the payload will execute onclick

Shown below, a raw socket message is intercepted and modified by adding an svg alert message payload


42["mp_chat_message",{"isSystem":false,"isLeader":true,"message":"Hey <svg/onload=alert('foo');>","from":{"id":"UocD_4qRZiXGbXf8AA-n","name":"alice"}}]

Impact: The impact of stored XSS in a chat room is severe. Once injected, the payload would be executed in the context of other user’s browsers who were within the same room. These payloads could be used to steal users authentication tokens, allowing complete account takeover. Making the vulnerability worse is the fact that tribe allows users to invite other’s to specefic chat rooms. Once a room has been successfully exploited with a XSS payload, a malicious user could then share the link to the specific chat room to others, increasing the number of potential victims.

Mitigation: The monkeyType developer eventually added client and serverside input validation to mitigate the impact of the vulnerability.

function sanitize(string) {
  const map = {
      '&': '&amp;',
      '<': '&lt;',
      '>': '&gt;',
      '"': '&quot;',
      "'": '&#x27;',
      "/": '&#x2F;',
  const reg = /[&<>"'/]/ig;
  return string.replace(reg, (match)=>(map[match]));

User Impersonation via Tribe Chat

Vulnerability: User messages in the Tribe Chat can be impersonated due to improper authorization in the implementation. Malicious users can abuse current socket message authentication measures to create messages that appear to come from other users or system.

Disclosure Method: According to the bug report policy at the time of discovery, I engaged the application developer on Discord Chat and opened a Github Issue

Proof of Concept:

  • Go to a tribe chat room, ex:
  • Send a message, capturing the message.

42["mp_chat_message",{"isSystem":false,"isLeader":true,"message":"Hey this is still alice","from":{"id":"UocD_4qRZiXGbXf8AA-n","name":"alice"}}]

  • Modify the name parameter, and re-send

42["mp_chat_message",{"isSystem":false,"isLeader":true,"message":"Hey this is still alice","from":{"id":"UocD_4qRZiXGbXf8AA-n","name":"bob"}}]

Impact: Malicious users can impersonate others in the chat room, which could enable abusive behavior negatively affecting users.

Mitigation: At the time this vulnerability was discovered, the application developer had already addressed the issue in a not yet released patch. On June 3rd, the patch was merged into the developmenet site at (see issue 1503)

Authenticated ByPass

Shown above, the leaderboard is spoofed using a crafted request seen here being sent in BurpSuite

Vulnerability: Users can bypass leaderboard controls and inject any object they want into the leaderboard by spoofing post requests to /checkLeaderboards. Malicious users can send specially crafted post requests and inject any user they want to the top of the leaderboard with any value words per minuet they want. Server does invalidate requests with cross-site scripting (XSS) payloads, therefore I believe this is not vulnerable to XSS.

Disclosure Method: For the first time, I submitted this vulnerability through, a bug bounty platform that rewards developers and bug hunters for traiged vulnerabilities in open-source software.

Proof of Concept: The following request will overwrite the leaderboard, injecting the user pwnville_foo into position 9 with a faked wpm of 200.

POST /checkLeaderboards HTTP/2
Content-Length: 750
Sec-Ch-Ua: " Not A;Brand";v="99", "Chromium";v="90"
Authorization: Bearer [redacted]
Sec-Ch-Ua-Mobile: ?0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36
Content-Type: application/json
Accept: */*
Sec-Fetch-Site: cross-site
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
Connection: close


Shown below, the fake user is now a top leader in words per minuete

Impact: Using this vulnerability, malicious users can overwrite the entire leaderboard with username strings of their choosing, which could be used to deface the website.

Migitaion: On the submission for this issue, the developer stated he is “Looking into moving to a token-based auth system for this endpoint. All the other cloud functions will be moved to the token system after this has been solved since the publicity of this (having the ability to alter public leaderboards) takes priority”

Drafting a Security Policy

Since there were several vulnerabilities discovered on the platform and no real vulnerability disclosure policy, I approached the developer on discord with an idea to add a policy. The developer welcome the idea, and we decided on using the security.txt standard of adding a disclosure policy under the path /.well-known/security.txt. The policy will tell researchers that new vulnerabilites can be disclosed to the devloper via email or private discord chat. We also added a security policy on the main website. Both of these pull requests can be found in #1505

Contact: message @Miodec on  
Expires: 2022-06-03T21:00:00.000Z  
Preferred-Languages: en  

Bug Bounty with Huntr.Dev

This was the first time I submitted a bug using the platformm and overall I was pleased with the experience. Huntr offers researchers an opportunity to get paid for disclosing vulnerabilities in open source software that does not already have a bug bounty program with the giants like hackerone or bugcrowd. The platform allows you to authenticate with GitHub and is fairly slick. To start this disclosure, I opened up a new issue on the platform and waited for the developer to respond with a patch. After the issue was fixed I was awarded a $40 dollar bounty. While it’s a small bounty, it’s a great way to organize your research and get paid while researching open source codebases.

Connect on Twitter