CVE-2022-3493
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 Human Resource Management System 1.0. This issue affects some unknown processing of the component Add Employee Handler. The manipulation of the argument First Name/Middle Name/Last Name leads to cross site scripting. The attack may be initiated remotely. The identifier VDB-210773 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 confidenceA stored cross-site scripting (XSS) vulnerability exists in SourceCodester HRMS 1.0's Add Employee Handler. The First Name, Middle Name, and Last Name fields do not properly sanitize user input, allowing injection of malicious JavaScript that executes when employee records are displayed.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify if SourceCodester/Oretnom23 HRMS 1.0 is installedCheck your web server for the HRMS application directory and review any version documentation or metadata files. If accessible, navigate to the main login page and look for version indicators in the footer or about page.Affected if The application is Oretnom23 Human Resource Management System version 1.0
-
Locate the employee database tableAccess the MySQL or MariaDB database used by the HRMS application. Look for a table that stores employee information, commonly named 'employee' or similar. Identify columns for first_name, middle_name, and last_name.Affected if A table exists with name fields that store unsanitized user input
-
Query for suspicious characters in name fieldsRun a SQL query to inspect name fields for potential XSS payloads. Example: SELECT id, first_name, middle_name, last_name FROM employees WHERE first_name LIKE '%<script%' OR middle_name LIKE '%<script%' OR last_name LIKE '%<script%';Affected if Any employee records contain HTML or JavaScript syntax like <script, <img, onload, or other XSS vectors in the name fields
-
Check if Add Employee form is accessibleLog into the HRMS as an administrator and navigate to the employee creation section. Verify that the form contains First Name, Middle Name, and Last Name input fields without visible sanitization.Affected if The Add Employee form exists and accepts these three name fields without apparent input validation
-
Verify stored XSS execution on employee displayCreate a test employee with a benign XSS payload in the First Name field (e.g., <img src=x onerror=alert(1)>), then view the employee list or details page to confirm the payload executes.Affected if The XSS payload executes when viewing the employee record, confirming the vulnerability is present and exploitable
You are affected if you are running Oretnom23 HRMS version 1.0 and have employee records in the database containing unsanitized name field data that executes JavaScript 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 proper input validation and output encoding for all name fields in the Add Employee handler. Sanitize stored data before rendering and use context-aware output encoding.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3493 — 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-2022-3493 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