CVE-2023-1961
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 SourceCodester Online Computer and Laptop Store 1.0. It has been classified as problematic. Affected is an unknown function of the file /admin/?page=system_info. The manipulation of the argument System Name leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-225348.
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 stored cross-site scripting (XSS) vulnerability exists in the admin panel of SourceCodester Online Computer and Laptop Store 1.0. The 'System Name' parameter on the /admin/?page=system_info page does not properly sanitize user input, allowing an attacker to inject malicious JavaScript that executes when the page is rendered.
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.
-
Identify the installed product versionLocate the application and confirm it is SourceCodester Online Computer and Laptop Store version 1.0. Check the application source files, about page, or any version indicator that confirms the exact version installed.Affected if The installed version is 1.0 of SourceCodester/Oretnom23 Online Computer and Laptop Store.
-
Access the admin panel loginNavigate to the /admin/ endpoint of the application and verify you can access the administrative interface. If credentials are required, use valid admin credentials.Affected if The admin panel is accessible at /admin/ and contains a system_info page.
-
Navigate to the System Name configuration pageVisit /admin/?page=system_info in the browser or via a web request tool. Identify the System Name input field on this page.Affected if The page contains a System Name parameter field that can be edited.
-
Inspect the current System Name value for XSS payloadsView the current value of the System Name parameter on the system_info page. Use browser developer tools or view the page source to see the raw HTML output of the System Name value.Affected if The System Name value contains unsanitized HTML/JavaScript tags such as <script>, <img onerror>, or other JavaScript event handlers that would execute if rendered.
-
Check stored database value for malicious inputIf you have database access, query the table storing system configuration (likely a system_info or settings table) and inspect the stored System Name value for XSS payloads.Affected if The database contains raw, unescaped XSS payloads in the System Name field.
You are affected if you are running version 1.0 of this product and the System Name on /admin/?page=system_info contains unsanitized script tags or event handlers that would execute when the page renders.
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 input validation and output encoding for the System Name parameter. Sanitize all user-supplied input before storage and apply context-aware output encoding when displaying the value.
- 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-1961 — 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-1961 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