Document Title:  
Tryton v5.4 - (Name) Persistent Cross Site Vulnerability  
References (Source):  
Release Date:  
Vulnerability Laboratory ID (VL-ID):  
Common Vulnerability Scoring System:  
Vulnerability Class:  
Cross Site Scripting - Persistent  
Current Estimated Price:  
500€ - 1.000€  
Product & Service Introduction:  
Tryton is business software, ideal for companies of any size, easy to  
use, complete and 100% Open Source. Tryton has  
a Three-tier architecture. It is composed of an application server which  
connects to a PostgreSQL database, a web or  
desktop client for the presentation and a set of server modules for the  
business logic. A docker container that comes  
pre-installed with the server, modules and web client. This is a very  
simple way of locally installing and exploring  
the application. It is also production ready for easy deployment. These  
images are updated every week.We also publish  
an optional add-on that can be used to manage timesheets from inside  
your browser. All the packages are also published  
on the Python Package Index. Available for os - arch linux, debian,  
fedora, gentoo, openbsd, ubuntu & netbsd.  
(Copy of the Homepage: & )  
Abstract Advisory Information:  
The vulnerability laboratory core research team discovered a persistent  
cross site web vulnerability in the Tryton v5.4.  
Affected Product(s):  
Tryton Foundation  
Product: Tryton v5.4 - CMS (Web-Application)  
Vulnerability Disclosure Timeline:  
2020-05-12: Public Disclosure (Vulnerability Laboratory)  
Discovery Status:  
Exploitation Technique:  
Severity Level:  
Authentication Type:  
Restricted authentication (user/moderator) - User privileges  
User Interaction:  
Low User Interaction  
Disclosure Type:  
Independent Security Research  
Technical Details & Description:  
A persistent input validation web vulnerability has been discovered in  
the official Tryton v5.4 web-application series.  
The vulnerability allows remote attackers to inject own malicious script  
codes with persistent attack vector to compromise  
browser to web-application requests from the application-side.  
The persistent vulnerability is located in the `name` parameter of the  
`User Profile` module. Remote attackers with low  
privileges are able to inject own malicious persistent script code as  
name for user accounts. The injected code can be  
used to attack the frontend or backend of the web-application. The  
request method to inject is POST and the attack vector  
is located on the application-side. Injection point is the profile input  
field with the name value and the execute occurs  
in the front ui on top right were the avatar is listed or in the admin  
backend on the res.user;name="Users"&views.  
Successful exploitation of the vulnerabilities results in session  
hijacking, persistent phishing attacks, persistent  
external redirects to malicious source and persistent manipulation of  
affected application modules.  
Request Method(s):  
[+] POST  
Vulnerable Module(s):  
[+] User Profile  
Vulnerable Input(s):  
[+] Name  
Vulnerable Parameter(s):  
[+] name  
Affected Module(s):  
[+] /index  
[+] /model/res.user;name="Users"&views (backend)  
Proof of Concept (PoC):  
The persistent web vulnerability can be exploited by low privileged web  
application user account with low user interaction.  
For security demonstration or to reproduce the vulnerability follow the  
provided information and steps below to continue.  
Manual steps to reproduce the vulnerability ...  
1. Open the application and login to your low privileged user account  
2. Move to the profile on top right side (click)  
3. Inject test payload to the "Name" input field and save the entry  
4. Execution occurs after save on top right and  
/model/res.user;name="Users"&views of the admin backend  
5. Successful reproduce of the persistent cross site vulnerability!  
PoC: Payload  
PoC: Vulnerable Source (Execution Point)  
<div class="input-group input-group-sm"><span  
class="input-group-btn"><button type="button" class="btn  
<input class="form-control mousetrap" placeholder="Search"  
autocomplete="off" list="ui-id-3"><datalist id="ui-id-3"></datalist>  
<span class="input-group-btn"><button type="button" class="btn  
btn-default hidden-md hidden-lg" aria-label="Clear Search"  
title="Clear Search" style="display: none;"><img class="icon"  
<button type="submit" class="btn btn-default" aria-label="Search"  
title="Search"><img class="icon"  
class="btn btn-default hidden-xs"  
type="button" title="Bookmark this filter" aria-label="Bookmark this  
filter"><img class="icon" aria-hidden="true"  
type="button" class="btn btn-default  
dropdown-toggle" data-toggle="dropdown" aria-expanded="false"  
aria-label="Bookmarks" title="Bookmarks" id="bookmarks" disabled="">  
<img aria-hidden="true" class="icon"  
<ul class="dropdown-menu dropdown-menu-right" role="menu"  
aria-labelledby="bookmarks"></ul><button type="button"  
class="btn btn-default hidden-xs" aria-expanded="false" aria-label="Show  
inactive records" title="Show inactive records">  
<img aria-hidden="true" class="icon"  
--- PoC Session Logs [POST] ---  
Host: tryton.localhost:8080  
Accept: application/json, text/javascript, */*; q=0.01  
Content-Type: application/json  
Authorization: Session  
X-Requested-With: XMLHttpRequest  
Content-Length: 527  
Origin: https://tryton.localhost:8080  
Connection: keep-alive  
Referer: https://tryton.localhost:8080/  
"company.rec_name":"Michael Scott Paper  
POST: HTTP/2.0 200 OK  
server: nginx/1.16.1  
content-type: application/json  
access-control-allow-origin: https://tryton.localhost:8080  
vary: Origin  
content-encoding: gzip  
Credits & Authors:  
Vulnerability-Lab -  
Benjamin Kunz Mejri -  
Disclaimer & Information:  
The information provided in this advisory is provided as it is without  
any warranty. Vulnerability Lab disclaims all warranties,  
either expressed or implied, including the warranties of merchantability  
and capability for a particular purpose. Vulnerability-Lab  
or its suppliers are not liable in any case of damage, including direct,  
indirect, incidental, consequential loss of business profits  
or special damages, even if Vulnerability-Lab or its suppliers have been  
advised of the possibility of such damages. Some states do  
not allow the exclusion or limitation of liability for consequential or  
incidental damages so the foregoing limitation may not apply.  
We do not approve or encourage anybody to break any licenses, policies,  
deface websites, hack into databases or trade with stolen data.  
Any modified copy or reproduction, including partially usages, of this  
file requires authorization from Vulnerability Laboratory.  
Permission to electronically redistribute this alert in its unmodified  
form is granted. All other rights, including the use of other  
media, are reserved by Vulnerability-Lab Research Team or its suppliers.  
All pictures, texts, advisories, source code, videos and other  
information on this website is trademark of vulnerability-lab team & the  
specific authors or managers. To record, list, modify, use or  
edit our material contact (admin@ or research@) to get a ask permission.  
Copyright © 2020 | Vulnerability Laboratory - [Evolution  
Security GmbH]™