dbcve.org
Car Listing Script PhpApplication · Gzscripts

CVE-2023-3556

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in GZ Scripts Car Listing Script PHP 1.8. It has been declared as problematic. This vulnerability affects unknown code of the file /preview.php. The manipulation of the argument page/sort_by leads to cross site scripting. The attack can be initiated remotely. VDB-233350 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A reflected cross-site scripting (XSS) vulnerability exists in GZ Scripts Car Listing Script PHP 1.8 in the /preview.php file. The page and sort_by parameters are not properly sanitized, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser when they access a crafted URL.

MitigationImplement proper input validation and output encoding on the page and sort_by parameters in preview.php. Use context-appropriate escaping and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Car Listing Script PhpApplication
Affected:= 1.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if GZ Scripts Car Listing Script PHP is installed
    Check your web server's document root for the Car Listing Script PHP files. Look for any version indicator files, admin panels, or footer files that may display the software version.
    Affected if The software is GZ Scripts Car Listing Script PHP version 1.8 exactly
  2. Locate the preview.php file
    Search the web root directory for preview.php. Common paths may include /preview.php or /path/to/carlisting/preview.php.
    Affected if The file preview.php exists in the web-accessible directory
  3. Verify the vulnerable parameters exist
    Open preview.php in a text editor or use 'grep -n "page\|sort_by" preview.php' to locate where the page and sort_by parameters are handled in the code.
    Affected if The file contains code that processes 'page' or 'sort_by' GET/POST parameters without visible sanitization functions
  4. Inspect input sanitization in preview.php
    Examine the code around line numbers where page/sort_by parameters are used. Look for functions like htmlspecialchars, strip_tags, or other sanitization routines applied to these parameters before output.
    Affected if No input validation or output encoding is applied to the page or sort_by parameters before they are echoed to the page
  5. Test parameter reflection (safe test)
    Access a URL like yoursite.com/preview.php?page=<test> or yoursite.com/preview.php?sort_by=<test> and view the page source to see if the <test> string appears unescaped in the HTML output.
    Affected if The parameter value is reflected in the HTML output without being HTML-encoded (e.g., < appears as < rather than &lt;)

You are affected if you are running GZ Scripts Car Listing Script PHP version 1.8 and the preview.php file reflects page or sort_by parameters without HTML encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on the page and sort_by parameters in preview.php. Use context-appropriate escaping and consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

Fix this in Car Listing Script Php Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-3556 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data