CVE-2023-7160
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 was found in SourceCodester Engineers Online Portal 1.0. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Add Engineer Handler. The manipulation of the argument first name/last name with the input <script>alert(0)</script> leads to cross site scripting. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-249182 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 · high confidenceStored cross-site scripting (XSS) vulnerability in SourceCodester Engineers Online Portal 1.0's Add Engineer Handler component. The first name and last name fields accept unsanitized input including script tags like <script>alert(0)</script>, allowing malicious JavaScript execution when viewed by other users.
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 installed product and versionIdentify the Engineers Online Portal installation and verify the version number is 1.0. Check application documentation, deployment records, or the application's version information page if available.Affected if The product is SourceCodester/Janobe Engineers Online Portal version 1.0
-
Verify Add Engineer Handler is accessibleLocate and access the Add Engineer Handler component within the portal's administrative or user management interface. This is typically found in the admin panel where new engineers are added.Affected if The Add Engineer Handler functionality exists and is accessible to users with appropriate permissions
-
Identify first name and last name input fieldsExamine the Add Engineer Handler form to confirm it contains first name and last name input fields. These are the vulnerable fields that accept unsanitized input.Affected if The form includes first name and/or last name input fields that accept user-supplied data
-
Test for input sanitizationAttempt to input a test payload such as <script>alert(0)</script> into the first name or last name field through the Add Engineer Handler. After submission, view the stored record to see if the script tag is rendered as-is or executed.Affected if The script tags or HTML elements are stored and displayed without encoding or sanitization, indicating the vulnerability is present
-
Inspect stored database recordsQuery the database or application storage where engineer records are kept. Examine the first_name and last_name fields directly to see if raw HTML/JavaScript is stored without encoding.Affected if The database contains raw HTML or script tags in the name fields, confirming unsanitized storage
The environment is affected if Engineers Online Portal version 1.0 is installed and the Add Engineer Handler stores first name or last name input without sanitization, allowing stored XSS to execute when viewed.
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/escaping on the first name and last name fields in the Add Engineer Handler to neutralize malicious payloads before storage and display.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7160 — 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-7160 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