CVE-2018-1000640: OpenCart-Overclocked Cross-site Scripting Vulnerability

Summary

14/05/2022
No i
Moderate
6.1

CVE-2018-1000640: OpenCart-Overclocked Cross-site Scripting Vulnerability. Affects villagedefrance/opencart-overclocked versions < 1.11.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

OpenCart-Overclocked is an open-source e-commerce platform that allows users to create and manage online stores. It is based on the popular OpenCart framework and provides additional features and enhancements. The vulnerability in OpenCart-Overclocked allows for the execution of arbitrary JavaScript code in the context of a victim's browser, leading to potential unauthorized actions, data access, session information theft, and denial of service attacks. This vulnerability arises from the lack of proper input sanitization in the OpenBay template of OpenCart-Overclocked.

Vulnerability Detail

The OpenCart-Overclocked OpenBay template does not sufficiently sanitize user-controlled input, resulting in a reflected Cross-Site Scripting (XSS) vulnerability. An attacker can exploit this vulnerability by coercing a user into visiting a specially crafted link containing the XSS payload. When the victim accesses the link, the malicious JavaScript code is executed in their browser, allowing the attacker to perform unauthorized actions and potentially gain access to sensitive information. The unsanitized input can be found in the 'openbay.tpl' file at line 95, where the 'token' variable is directly echoed without proper sanitization.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

A temporary workaround for this vulnerability is to manually sanitize the 'token' variable in the 'openbay.tpl' file. This can be done by using the PHP 'htmlspecialchars' function to escape special characters. The modified code would look like this:

var token = "<?php echo htmlspecialchars($_GET['token'], ENT_QUOTES, 'UTF-8'); ?>";

Conclusion

The OpenCart-Overclocked OpenBay template is vulnerable to a reflected Cross-Site Scripting (XSS) attack due to insufficient input sanitization. This vulnerability can be exploited by tricking users into visiting malicious links. To mitigate the risk, it is crucial to implement proper input sanitization techniques and keep the software up to date. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for villagedefrance/opencart-overclocked →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary JavaScript code in the context of a victim's browser. This can lead to unauthorized actions, data access, session information theft, and denial of service attacks.

An attacker can exploit this vulnerability by tricking a user into visiting a specially crafted link containing the XSS payload. When the victim accesses the link, the malicious JavaScript code is executed in their browser.

Yes, the vulnerability can be fixed by implementing proper input sanitization and validation techniques. It is recommended to sanitize all user-controlled input to prevent the execution of malicious code.

A temporary workaround is to manually sanitize the 'token' variable in the 'openbay.tpl' file using the PHP 'htmlspecialchars' function.

To protect your installation, make sure to apply the recommended fix by implementing proper input sanitization and validation. Additionally, keep your software up to date with the latest security patches and releases.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback