dbcve.org
Event Registration SystemApplication · Rinvizle

CVE-2022-4233

MEDIUM · 6.1 CVSS v3.1 Published 2022-11-30
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 Event Registration System 1.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /event/admin/?page=user/list. The manipulation of the argument First Name/Last Name leads to cross site scripting. The attack can be launched remotely. The associated identifier of this vulnerability is VDB-214591.

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

Stored cross-site scripting (XSS) vulnerability in SourceCodester Event Registration System 1.0 admin panel at /event/admin/?page=user/list. The First Name and Last Name fields do not properly sanitize user input, allowing remote attackers to inject malicious JavaScript that executes when administrators view the user list.

MitigationImplement proper input validation and output encoding for all user-supplied fields, particularly First Name and Last Name. Apply context-appropriate escaping when rendering user data in HTML. Consider implementing a Content Security Policy (CSP) header 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
Event Registration 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. Identify the installed Event Registration System version
    Check your web application files, package.json, or admin interface for the software version. For SourceCodester Event Registration System, look in the source code headers or configuration files for version 1.0.
    Affected if The software version is SourceCodester Event Registration System 1.0 or Rinvizle Event Registration System 1.0
  2. Verify the admin panel is accessible
    Attempt to access the admin panel endpoint at /event/admin/?page=user/list through your web server. Check if the page loads and requires authentication.
    Affected if The admin panel at /event/admin/?page=user/list is accessible and displays a user list
  3. Confirm user creation or registration functionality exists
    Check if your installation has functionality that allows creating users or allowing public registration where First Name and Last Name fields can be submitted.
    Affected if Users can be created or registered with First Name and Last Name fields through the application
  4. Inspect the database for anomalous name entries
    Query your database users table (commonly named users, tbl_users, or similar) and examine the first_name and last_name columns for any entries containing HTML, JavaScript tags, or script-related keywords.
    Affected if Any user records contain unescaped HTML or JavaScript code in First Name or Last Name fields
  5. View the admin user list as an administrator
    Log in as an administrator and navigate to /event/admin/?page=user/list. Observe if any user names render as executable code or trigger JavaScript execution.
    Affected if User names from step 4 render as active HTML/JavaScript when viewed in the admin user list

You are affected if you run Event Registration System version 1.0 and have any user records containing unsanitized First Name or Last Name values that execute when viewed in the admin panel.

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 input validation and output encoding for all user-supplied fields, particularly First Name and Last Name. Apply context-appropriate escaping when rendering user data in HTML. Consider implementing a Content Security Policy (CSP) header as a defense-in-depth measure.

Fix this in Event Registration System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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