CVE-2023-3659
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 has been found in SourceCodester AC Repair and Services System 1.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file admin/?page=user/manage_user. The manipulation of the argument firstname/middlename leads to cross site scripting. The attack can be launched remotely. The identifier VDB-234013 was 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in SourceCodester AC Repair and Services System 1.0 within the admin/?page=user/manage_user functionality. The firstname and middlename parameters accept unsanitized user input, allowing injection of malicious JavaScript that executes when other users view the user management page.
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= 1.0CVSS 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.
-
Confirm AC Repair and Services System installationLocate the web application directory and check for version identifier in source files, typically in a config file, header comment, or README. Common paths: /var/www/html/[appname] or C:\xampp\htdocs\[appname]Affected if The application is SourceCodester AC Repair and Services System version 1.0
-
Verify admin panel accessibilityNavigate to admin/?page=user/manage_user or attempt to access this URL path in the running applicationAffected if The admin user management page is accessible without additional authentication barriers beyond normal login
-
Inspect firstname and middlename input handlingReview the PHP source code handling the user creation/update form at admin/?page=user/manage_user. Locate the code that processes the firstname and middlename POST parametersAffected if The code accepts and stores firstname/middlename input without applying htmlspecialchars, ENT_QUOTES, or equivalent output encoding before database insertion or display
-
Check database storage of user fieldsQuery the users table in the database to examine stored values for firstname and middlename columns. Look for unescaped HTML characters in existing recordsAffected if The database contains raw HTML/JavaScript in firstname or middlename fields without encoded entities
-
Test XSS execution on user management pageCreate or edit a user with a test payload such as <script>alert(1)</script> in the firstname or middlename field, then view the user management page as another userAffected if The payload executes as JavaScript when the page renders, confirming the XSS vulnerability is present and exploitable
A user is affected if they run AC Repair and Services System version 1.0 and the application allows unauthenticated or low-privilege users to access the user management functionality with unsanitized firstname/middlename fields.
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 the firstname and middlename fields. Use context-aware sanitization (e.g., htmlspecialchars with ENT_QUOTES) before displaying user data, and apply a Content Security Policy as defense-in-depth.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3659 — 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-3659 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