dbcve.org
ChaincityApplication · Bugfinder

CVE-2023-3794

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-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 classified as problematic has been found in Bug Finder ChainCity Real Estate Investment Platform 1.0. Affected is an unknown function of the file /chaincity/user/ticket/create of the component New Ticket Handler. The manipulation of the argument subject leads to cross site scripting. It is possible to launch the attack remotely. VDB-235062 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in the ChainCity Real Estate Investment Platform 1.0. The 'subject' parameter in the ticket creation form at /chaincity/user/ticket/create lacks proper input sanitization, allowing attackers to inject malicious JavaScript that executes when other users view the created ticket.

MitigationImplement server-side input validation and output encoding for the subject field and all user-supplied data. Use established sanitization libraries (e.g., DOMPurify, OWASP Java Encoder) to neutralize script tags and XSS vectors before storing and displaying user input.

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
ChaincityApplication
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 ChainCity platform installation
    Locate the web application's installation directory and identify the exact version of the ChainCity Real Estate Investment Platform. Check version files, README, or application metadata for version number 1.0.
    Affected if The installed version is ChainCity Real Estate Investment Platform 1.0.
  2. Verify ticket creation endpoint exists
    Access the URL path /chaincity/user/ticket/create in the web browser or via an HTTP request tool. Confirm the ticket creation form is accessible and includes a 'subject' input field.
    Affected if The ticket creation form at /chaincity/user/ticket/create is accessible and contains a subject parameter field.
  3. Check input sanitization on subject field
    Review the server-side code handling the ticket creation form, specifically the code processing the 'subject' parameter. Look for input validation, sanitization, or output encoding functions applied before storing the subject value.
    Affected if The subject parameter lacks server-side input validation or sanitization (no sanitization library, regex filter, or encoding function is applied).
  4. Test for stored XSS in subject field
    Submit a test ticket with a benign XSS payload in the subject field (such as <script>alert(1)</script> or <img src=x onerror=alert(1)>). Save the ticket and then view it as a different user to see if the script executes.
    Affected if The submitted JavaScript payload executes when viewing the ticket, indicating the stored XSS vulnerability is present.

A user is affected if the ChainCity Real Estate Investment Platform version 1.0 is installed, the ticket creation form at /chaincity/user/ticket/create is accessible, and the subject parameter lacks proper server-side input sanitization allowing stored JavaScript to execute when tickets are viewed.

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 server-side input validation and output encoding for the subject field and all user-supplied data. Use established sanitization libraries (e.g., DOMPurify, OWASP Java Encoder) to neutralize script tags and XSS vectors before storing and displaying user input.

Fix this in Chaincity 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-3794 — 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-3794 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