dbcve.org
E Commerce SystemApplication · E Commerce System Project

CVE-2023-1557

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 SourceCodester E-Commerce System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /ecommerce/admin/user/controller.php?action=edit of the component Username Handler. The manipulation of the argument USERID leads to improper access controls. The attack may be launched remotely. VDB-223550 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

IDOR/broken access control vulnerability in SourceCodester E-Commerce System 1.0's admin user edit functionality. The USERID parameter can be manipulated to modify other users' accounts without proper authorization, likely allowing privilege escalation or unauthorized data modification.

MitigationImplement proper server-side authorization checks to verify the requesting user has permission to edit the target user account. Use indirect object references and validate session authentication before any user data modifications.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the installed application is SourceCodester E-Commerce System 1.0
    Locate the application in your web root directory and check the version identifier in the main PHP files (often in header comments, README files, or a dedicated version/config file). Compare your version to the affected range.
    Affected if The application version is exactly 1.0 of SourceCodester E-Commerce System.
  2. Verify the admin panel user management feature exists and is accessible
    Navigate to the admin panel and locate the user management or user edit section. Typical paths include /admin/users.php, /admin/edit_user.php, or similar. Confirm the functionality is present and operational.
    Affected if The admin user edit functionality is present and enabled in the application.
  3. Locate the user edit handler script that processes the USERID parameter
    Search the application source code for files handling user profile updates, such as edit_user.php, user_edit.php, or user_update.php. Identify the script that processes the USERID parameter used in the edit request.
    Affected if A user edit script exists that accepts and processes a USERID parameter without proper validation.
  4. Inspect the user edit code for authorization logic
    Open the identified user edit handler file and examine the code between parameter receipt and database update. Look for session validation, permission checks, or ownership verification before allowing modifications to user records.
    Affected if The code lacks proper server-side authorization checks to verify the requesting user has permission to edit the target user account.
  5. Test for IDOR vulnerability by attempting to manipulate the USERID parameter
    Using a web proxy or browser developer tools, access the user edit form for your own admin account. Intercept the request and modify the USERID parameter value to point to a different user account, then submit the request. Observe whether the modification succeeds without proper authorization.
    Affected if The application allows modification of another user's account by changing the USERID parameter value in the request.

The environment is affected if SourceCodester E-Commerce System version 1.0 is installed and the admin user edit functionality permits unauthorized modification of user accounts via the USERID parameter.

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 proper server-side authorization checks to verify the requesting user has permission to edit the target user account. Use indirect object references and validate session authentication before any user data modifications.

Fix this in E Commerce System 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-1557 — 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-1557 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