dbcve.org
Gz Forum ScriptApplication · Gzscripts

CVE-2023-3554

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 GZ Forum Script 1.8 and classified as problematic. Affected by this issue is some unknown functionality of the file /preview.php. The manipulation of the argument catid/topicid/topic/topic_message/free_name leads to cross site scripting. The attack may be launched remotely. The identifier of this vulnerability is VDB-233348. 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 stored Cross-Site Scripting (XSS) vulnerability exists in GZ Forum Script 1.8 within the /preview.php file. Multiple parameters (catid, topicid, topic, topic_message, free_name) fail to properly sanitize user input before rendering it back in the application, allowing remote attackers to inject malicious JavaScript that executes in victim browsers.

MitigationImplement context-aware output encoding and input validation for all user-supplied parameters in preview.php. Deploy a WAF with XSS filtering rules as an interim protective measure until a vendor patch is available.

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
Gz Forum ScriptApplication
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. Confirm GZ Forum Script installation
    Identify if the GZ Forum Script web application is present on the server by checking for forum-related directories or files, or by accessing the site and identifying the forum software through its interface or page source.
    Affected if The application is not GZ Forum Script or the software cannot be identified as this product.
  2. Verify installed version is 1.8
    Locate version information in the application by checking for a version file, admin panel about page, or footer text. Common paths include /admin/, /includes/, or the main index file source.
    Affected if The installed version is not exactly 1.8 (versions other than 1.8 are not affected by this specific CVE).
  3. Confirm preview.php exists and is accessible
    Check for the presence of preview.php in the web root directory. Attempt to access it directly via HTTP request to verify it is functional.
    Affected if The preview.php file does not exist or is not accessible on the server.
  4. Inspect preview.php for vulnerable parameters
    Review the source code of preview.php to identify if parameters catid, topicid, topic, topic_message, or free_name are processed and output without sanitization. Search for echo, print, or variable output statements involving these parameters.
    Affected if The code shows these parameters are output directly without encoding, validation, or sanitization functions.
  5. Test parameter reflection in preview.php
    Submit a test request to preview.php with harmless test values in the vulnerable parameters (catid, topicid, topic, topic_message, free_name) and verify if the values are reflected back in the response unescaped.
    Affected if The submitted parameter values appear in the response HTML without being escaped (visible as raw input rather than encoded entities).

A user is affected if GZ Forum Script version 1.8 is installed, preview.php exists, and user-supplied input in catid, topicid, topic, topic_message, or free_name parameters is reflected without sanitization.

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 context-aware output encoding and input validation for all user-supplied parameters in preview.php. Deploy a WAF with XSS filtering rules as an interim protective measure until a vendor patch is available.

Fix this in Gz Forum Script Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3554 — 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-3554 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