CVE-2023-1690
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, which was classified as problematic, has been found in SourceCodester Earnings and Expense Tracker App 1.0. This issue affects some unknown processing of the file LoginRegistration.php?a=register_user. The manipulation of the argument fullname leads to cross site scripting. The attack may be initiated remotely. The identifier VDB-224309 was 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 · high confidenceReflected XSS vulnerability in SourceCodester Earnings and Expense Tracker App 1.0's registration page (LoginRegistration.php). The fullname parameter submitted via the register_user action is not properly sanitized before being reflected back in the response, allowing injection of arbitrary JavaScript code.
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.
-
Locate the application installationSearch for the file LoginRegistration.php in your web server's document root or application directory. This is typically found in the main project folder of SourceCodester Earnings and Expense Tracker App.Affected if The file LoginRegistration.php exists in your environment
-
Confirm the application versionCheck for a version file, README.txt, or any version indicator within the project directory. Look for version: 1.0 or examine the application footer/admin pages for version information.Affected if The installed version is 1.0 of Earnings and Expense Tracker App
-
Verify the fullname parameter handling in codeOpen LoginRegistration.php and locate the code that handles the register_user action. Search for where the fullname parameter is processed and reflected back in the response. Check if htmlspecialchars, htmlentities, or any output encoding function is applied to the fullname variable before output.Affected if The fullname parameter is echoed back in the response without proper output encoding (htmlspecialchars with ENT_QUOTES)
-
Test fullname parameter for XSS reflectionAccess the registration page and submit a test fullname value such as <script>alert(1)</script> via the register_user action. Inspect the response to see if the script tags are rendered literally or executed.Affected if The submitted fullname value is reflected in the response without being entity-encoded
You are affected if you have Earnings and Expense Tracker App version 1.0 installed with LoginRegistration.php present and the fullname parameter is reflected without HTML entity encoding.
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 output encoding for the fullname parameter when displaying user input, and add server-side input validation to reject special characters typically used in XSS attacks.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1690 — 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-1690 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