dbcve.org
E Commerce SystemApplication · E Commerce System Project

CVE-2023-1507

MEDIUM · 6.1 CVSS v3.1 Published 2023-03-20
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 has been found in SourceCodester E-Commerce System 1.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /ecommerce/admin/category/controller.php of the component Category Name Handler. The manipulation of the argument CATEGORY leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-223411.

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

Cross-site scripting (XSS) vulnerability in SourceCodester E-Commerce System 1.0's category name handler. The CATEGORY parameter in /ecommerce/admin/category/controller.php is not properly sanitized, allowing injection of malicious JavaScript code through user-supplied input.

MitigationImplement input validation and output encoding for the CATEGORY parameter. Use context-appropriate escaping when rendering category names in HTML, and consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.

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
E Commerce SystemApplication
Affected:= 1.0

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. Confirm SourceCodester E-Commerce System is installed
    Locate the ecommerce application directory in the web server root. Common paths include /var/www/html/ecommerce or C:\inetpub\wwwroot\ecommerce. Look for index.php or admin/ directory structure.
    Affected if The ecommerce application directory exists on the server
  2. Verify the installed version is 1.0
    Search for a version file such as version.php, README.txt, or config.php within the application root that explicitly states version 1.0.
    Affected if The version is identified as 1.0
  3. Check if the vulnerable category controller exists
    Verify the file /ecommerce/admin/category/controller.php exists in the web root directory.
    Affected if The file controller.php exists in the /ecommerce/admin/category/ directory
  4. Confirm admin access to the category management feature
    Navigate to the admin category management interface at /ecommerce/admin/category/ or equivalent path to verify the module is enabled and accessible.
    Affected if The admin category module is accessible and functional
  5. Verify the CATEGORY parameter accepts unsanitized input
    Submit a test request to the category controller containing the CATEGORY parameter with a benign test string (such as <script>test</script>), then view the category list output to confirm whether the input is rendered without HTML encoding.
    Affected if The CATEGORY parameter value is reflected in the HTML output without escaping special characters

The environment is affected if SourceCodester E-Commerce System version 1.0 is installed with the admin category module accessible and the CATEGORY parameter accepts and reflects user-supplied input without HTML 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

Implement input validation and output encoding for the CATEGORY parameter. Use context-appropriate escaping when rendering category names in HTML, and consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.

Fix this in E Commerce System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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