CVE-2023-1689
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 classified as problematic was found in SourceCodester Earnings and Expense Tracker App 1.0. This vulnerability affects unknown code of the file Master.php?a=save_earning. The manipulation of the argument name leads to cross site scripting. The attack can be initiated remotely. The identifier of this vulnerability is VDB-224308.
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 confidenceThe SourceCodester Earnings and Expense Tracker App 1.0 contains a stored cross-site scripting (XSS) vulnerability in Master.php (action=save_earning). The 'name' parameter is not properly sanitized before storage, allowing malicious JavaScript to be injected and executed in browsers of users who view the data.
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.
-
Confirm the application is installedIdentify if the SourceCodester Earnings and Expense Tracker App is running in your environment by locating the web application files or checking running web servicesAffected if The application is present and accessible in your environment
-
Verify the application versionCheck the installed version of the Earnings and Expense Tracker App against version 1.0Affected if The installed version is exactly 1.0 or within the affected range (1.0)
-
Locate Master.php with save_earning actionSearch the application source code for the file Master.php that handles the action=save_earning parameterAffected if The file Master.php exists and processes the save_earning action
-
Inspect the name parameter handlingExamine the source code in Master.php to see how the 'name' parameter is handled - look for whether it is sanitized, escaped, or validated before being stored in the databaseAffected if The 'name' parameter is processed and stored without proper sanitization (no htmlspecialchars or equivalent escaping)
-
Test for stored XSS injectionSubmit a test payload containing HTML/JavaScript characters (e.g., <script>alert('XSS')</script>) in the 'name' parameter via the save_earning action, then retrieve the stored data to see if the payload executesAffected if The malicious payload is stored and rendered without encoding, executing in the browser
You are affected if you are running Earnings and Expense Tracker App version 1.0 and the 'name' parameter in Master.php (action=save_earning) is not sanitized before storage and output, allowing stored XSS execution.
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 input validation and output encoding: sanitize the 'name' parameter using appropriate escaping functions (htmlspecialchars) before storage and before rendering in any output context to prevent script injection.
- 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-1689 — 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-1689 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