dbcve.org
Event ScriptApplication · Simplephpscripts

CVE-2023-3475

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-30
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 SimplePHPscripts Event Script 2.1 and classified as problematic. Affected by this issue is some unknown functionality of the file preview.php of the component URL Parameter Handler. The manipulation leads to cross site scripting. The attack may be launched remotely. It is recommended to upgrade the affected component. VDB-232754 is the identifier assigned to this vulnerability.

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 · moderate confidence

A cross-site scripting (XSS) vulnerability exists in SimplePHPscripts Event Script 2.1 within the preview.php file's URL parameter handling functionality. The vulnerability allows remote attackers to inject malicious scripts through unsanitized URL parameters. Exploitation requires tricking users into clicking crafted URLs.

MitigationUpgrade SimplePHPscripts Event Script to a version newer than 2.1 that includes proper input sanitization in preview.php, or implement output encoding/validation on the URL parameter handler.

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
Event ScriptApplication
Affected:= 2.1

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 SimplePHPscripts Event Script is installed
    Search the web server filesystem for event script PHP files, or check the application footer/admin panel for version information
    Affected if The application is SimplePHPscripts Event Script version 2.1
  2. Locate the preview.php file
    Search the web document root for preview.php, typically found in the main application directory
    Affected if The file preview.php exists in the web-accessible directory
  3. Verify the installed version is 2.1
    Check version files, config files, or source code comments within the Event Script installation for the exact version number
    Affected if The installed version is exactly 2.1
  4. Confirm the application handles URL parameters
    Review preview.php source code to identify if it processes URL parameters without sanitization, specifically looking for $_GET or $_REQUEST usage
    Affected if preview.php processes URL parameters without proper input sanitization or output encoding
  5. Determine if the application is network accessible
    Check if the web server hosting the Event Script is reachable from user browsers or external networks
    Affected if The vulnerable preview.php is accessible to end users via HTTP/HTTPS

If SimplePHPscripts Event Script version 2.1 is installed and the preview.php file processes URL parameters without sanitization, the environment is affected by this XSS vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SimplePHPscripts Event Script to a version newer than 2.1 that includes proper input sanitization in preview.php, or implement output encoding/validation on the URL parameter handler.

Recommended fix Moderate confidence

latest stable release of Event Script (version >2.1)

  1. 1. Download the latest version of SimplePHPscripts Event Script from the official vendor website or repository
  2. 2. Before applying the upgrade, perform a complete backup of the current website files and database
  3. 3. Review the changelog or release notes for version 2.1+ to confirm the XSS vulnerability in preview.php has been addressed
  4. 4. Upload and replace the existing files with the new version files
  5. 5. Verify that the preview.php file has been updated and the URL parameter handling is now properly sanitized
  6. 6. Test the application to confirm the XSS vulnerability is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Event Script 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-3475 — 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-3475 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