dbcve.org
Classified Ads Script PhpApplication · Simplephpscripts

CVE-2023-3465

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-29
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 Classified Ads Script 1.8. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file user.php of the component HTTP POST Request Handler. The manipulation of the argument title leads to cross site scripting. The attack can be launched remotely. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-232711.

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 SimplePHPscripts Classified Ads Script 1.8 within the user.php file's HTTP POST Request Handler. The 'title' parameter is not properly sanitized before being stored and rendered, allowing an attacker to inject malicious JavaScript code that executes in the context of other users' browsers.

MitigationUpgrade the affected component to the latest version, or implement proper input validation and output encoding/escaping on the 'title' parameter in user.php to prevent XSS execution.

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
Classified Ads 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 the installed version of SimplePHPscripts Classified Ads Script
    Check the source code, README, or any version file in the web root for the application version. Alternatively, view the HTML source of any page for version comments or check the admin panel for version information.
    Affected if The installed version is exactly 1.8 (Simplephpscripts Classified Ads Script Php version 1.8)
  2. Locate the user.php file in the web application
    Search the web root directory for user.php. This file handles HTTP POST requests and contains the vulnerable 'title' parameter handler.
    Affected if The user.php file exists in the application directory and processes POST requests with a 'title' parameter
  3. Inspect the user.php code for input sanitization on the 'title' parameter
    Open user.php and search for the code that handles the 'title' POST parameter. Look for functions like htmlspecialchars, strip_tags, or any sanitization/validation functions applied to the 'title' before storing it in the database.
    Affected if The 'title' parameter is processed and stored without proper sanitization (no htmlspecialchars, strip_tags, or similar escaping functions found)
  4. Verify the application stores and displays user-submitted ads
    Log in as a user and attempt to create a new classified ad with a 'title' field. Submit the form and then view the ad listing page to confirm the title is rendered and stored in the database.
    Affected if The application allows unauthenticated or authenticated users to submit ads with a title that gets stored and displayed back to users
  5. Confirm no output encoding is applied when titles are rendered
    View the page where ads are displayed (such as the main listing or ad detail page) and examine the source code to see if the displayed title contains raw HTML/JavaScript without encoding.
    Affected if The title field from stored ads is rendered in HTML without output encoding, allowing script execution

You are affected if you have SimplePHPscripts Classified Ads Script version 1.8 installed and the user.php file processes the 'title' parameter without sanitization or output 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

Upgrade the affected component to the latest version, or implement proper input validation and output encoding/escaping on the 'title' parameter in user.php to prevent XSS execution.

Fix this in Classified Ads Script Php Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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