Exploit/Advisories

Published on April 28th, 2020 📆 | 6972 Views ⚑

0

POS PHP 17.5 Cross Site Scripting ↭


https://www.ispeech.org

Document Title:
===============
POS PHP v17.5 - Persistent Cross Site Web Vulnerability

References (Source):
====================
https://www.vulnerability-lab.com/get_content.php?id=2228

Release Date:
=============
2020-04-28

Vulnerability Laboratory ID (VL-ID):
====================================
2228

Common Vulnerability Scoring System:
====================================
4.6

Vulnerability Class:
====================
Cross Site Scripting - Persistent

Current Estimated Price:
========================
1.000€ - 2.000€

Product & Service Introduction:
===============================
Turn your Retail Small Business into a Customer Focused, Profit
Generating Machine. Guaranteed to save you time,
increase the accuracy of your inventory, and help you make informed
decisions for your business. Types of businesses
that work great with PHP Point of Sale.

(Copy of the Homepage: https://phppointofsale.com/ )

Abstract Advisory Information:
==============================
The vulnerability laboratory core research team discovered a persistent
cross site scripting web vulnerability in the POS PHP v17.5 web-application.

Vulnerability Disclosure Timeline:
==================================
2020-04-28: Public Disclosure (Vulnerability Laboratory)

Discovery Status:
=================
Published

Exploitation Technique:
=======================
Remote

Severity Level:
===============
Medium

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 POS PHP v17.5 web-application.
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 web vulnerability is located in the firstname and
lastname parameter of the customer profile module.
Remote attackers are able to change or add malicious script code as
firstname and lastname to customer profiles.
Thus allows to execute the script code with persistent attack vector
against administrators in the backend in the
/customers/ or customers/save/ modules. The request method to inject is
POST via add or edit of the customer and
the attack vector is located on the application-side.





Successful exploitation of the vulnerability 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):
[+] Customer (index.php/customers/save)

Vulnerable Input(s):
[+] Firstname
[+] Lastname

Vulnerable File(s):
[+]

Vulnerable Parameter(s):
[+] firstname
[+] lastname

Affected Module(s):
[+] index.php/customers/

Proof of Concept (PoC):
=======================
The persistent input validation web vulnerability can be exploited by
remote attackers with low privilege user account with low user interaction.
For security demonstration or to reproduce the security web
vulnerability follow the provided information and steps below to continue.

Manual steps to reproduce ...
1. Register a customer account
2. Move to the profile section
3. Inject test payload into the vulnerable firstname and lastname input
field
4. Save the entry and wait
Note: The execute occurs in the backend on preview of barcode, customer
details and more
5. Wait until the admin or other high privileged user roles are
interacting for execute
6. Successful reproduce of the persistent web vulnerability!

PoC: Exploitation

PoC: Vulnerable Source
Reports - PHP Point Of Sale, Inc "onload="alert(document.cookie)"> >"onload=alert(document.cookie)>
Report04/25/2019-04/25/2020


Source link

Tagged with:



Comments are closed.