CVE-2023-3535
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 · uneditedA vulnerability was found in SimplePHPscripts FAQ Script PHP 2.3. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /preview.php of the component URL Parameter Handler. The manipulation leads to cross site scripting. The attack can be launched remotely. The associated identifier of this vulnerability is VDB-233287.
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 confidenceA Cross-Site Scripting (XSS) vulnerability in SimplePHPscripts FAQ Script PHP 2.3's preview.php file allows remote attackers to inject malicious scripts via unsanitized URL parameters in the URL Parameter Handler component.
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= 2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SimplePHPscripts FAQ Script is installedSearch the web server for the FAQ Script PHP installation directories or files, commonly found in /faq/, /scripts/faq/, or the web root.Affected if The SimplePHPscripts FAQ Script PHP application is present on the server
-
Determine the installed version of the FAQ ScriptCheck version.php, README, or any version file within the FAQ Script installation directory for the exact version number.Affected if The installed version is exactly 2.3
-
Locate the preview.php fileFind preview.php within the FAQ Script installation directory, typically at /path/to/faq/preview.php or similar.Affected if The file preview.php exists in the installation
-
Check if the URL Parameter Handler processes input without sanitizationExamine the preview.php source code for how URL parameters are handled - look for $_GET, $_REQUEST, or similar superglobals used without sanitization functions like htmlspecialchars, htmlentities, or parameter binding.Affected if URL parameters are processed and output without proper sanitization in preview.php
-
Test for XSS via URL parametersSend a crafted request to preview.php with a test XSS payload in a URL parameter (for example: ?param=<script>alert(1)</script>) and observe if the payload is reflected unescaped in the response.Affected if The malicious script payload is reflected in the page output without encoding
A server is affected if it runs SimplePHPscripts FAQ Script PHP version 2.3 with the preview.php file accessible and its URL parameters processed without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and output encoding for all URL parameters in preview.php to prevent XSS attacks.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-3535 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3535 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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