CVE-2018-18785

An issue was discovered in zzcms 8.3

published October 29, 2018

CVSS
—
EPSS
1%
Percentile
68.0
In the wild
Unconfirmed
What it is

⚠️ A sneaky SQL injection hides in zzcms 8.3, waiting for a crafty cookie to lead the way! 🍪 Think of this vulnerability like a sneaky backdoor in a restaurant where the staff unknowingly lets in a hungry customer who can order anything without paying. If the kitchen isn't vigilant, that customer could literally walk away with the whole cake! An attacker could exploit this vulnerability to manipulate SQL queries, potentially allowing them to view, modify, or delete database records. This could lead to unauthorized access to sensitive data, and in the worst-case scenario, a complete compromise of the database!

Put simply

Think of this vulnerability like a sneaky backdoor in a restaurant where the staff unknowingly lets in a hungry customer who can order anything without paying. If the kitchen isn't vigilant, that customer could literally walk away with the whole cake! The vulnerability in zzcms exists due to a lack of proper sanitization on inputs coming from the `zzcmscpid` cookie, allowing attackers to inject malicious SQL commands through the `zs/search.php` script.

What to do

An attacker could exploit this vulnerability to manipulate SQL queries, potentially allowing them to view, modify, or delete database records. This could lead to unauthorized access to sensitive data, and in the worst-case scenario, a complete compromise of the database! To safeguard against this, developers should update to a fixed version of zzcms if available, implement prepared statements to mitigate SQL injection risks, and ensure all user inputs are thoroughly validated and sanitized. Additionally, conducting regular security audits is a good practice! You've got this! With some attention to security, you can keep your application safe and sound! 🛡️

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.01202 · 68.0th percentile
Published
2018-10-29T05:00Z
EPSS history
Timeline
  • 29 OCT 05:00Z
    An issue was discovered in zzcms 8.3
    cvelistv5