dbcve.org
Maid Hiring Management SystemApplication · Phpgurukul

CVE-2023-37744

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-13
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
Maid Hiring Management System v1.0 was discovered to contain a cross-site scripting (XSS) vulnerability via the component /admin/search-booking-request.php.

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 confidence

A stored cross-site scripting (XSS) vulnerability exists in the Maid Hiring Management System v1.0 within the admin panel's search-booking-request.php component. The vulnerability allows injection of malicious JavaScript code through unsanitized user input in the booking request search functionality.

MitigationImplement proper input validation and output encoding for all user-supplied data in the search-booking-request.php file. Apply context-aware sanitization (e.g., htmlspecialchars for HTML context) and consider implementing a Content Security Policy header to mitigate XSS execution.

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
Maid Hiring Management SystemApplication
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. Identify the installed application
    Locate the Maid Hiring Management System by searching for its characteristic files such as index.php, admin/index.php, or the presence of a 'maid-hiring' directory. Check the application's version in any about.php, readme.txt, or version file if available.
    Affected if The application is Phpgurukul Maid Hiring Management System version 1.0
  2. Verify the affected file exists
    Check for the presence of the search-booking-request.php file in the admin panel directory. Typical path would be /admin/search-booking-request.php or within an admin/ subdirectory.
    Affected if The file search-booking-request.php exists in the admin directory
  3. Confirm admin panel access
    Attempt to access the admin login page and verify the admin panel is accessible. The vulnerability exists in the admin panel's search functionality, so admin access is required to trigger the XSS vector.
    Affected if The admin panel is accessible and search-booking-request.php can be accessed via browser or direct request
  4. Inspect input handling in the vulnerable file
    Examine the source code of search-booking-request.php for how user-supplied input in the booking request search field is handled. Look for direct use of $_POST or $_GET parameters without sanitization functions like htmlspecialchars, htmlentities, or similar.
    Affected if The code directly outputs user input without sanitization functions (e.g., no htmlspecialchars() wrapping of search parameters before output)
  5. Check for stored XSS payloads in the database
    If the application database is accessible, inspect tables related to booking requests (e.g., tblbooking, booking_requests) for any suspicious script tags, iframe elements, or JavaScript event handlers that may have been injected.
    Affected if The booking request database tables contain unsanitized script tags or JavaScript code injected by an attacker

A user is affected if they are running Maid Hiring Management System version 1.0 with the admin panel accessible and the search-booking-request.php file present, where the search functionality does not sanitize user input before rendering it in the HTML output.

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 proper input validation and output encoding for all user-supplied data in the search-booking-request.php file. Apply context-aware sanitization (e.g., htmlspecialchars for HTML context) and consider implementing a Content Security Policy header to mitigate XSS execution.

Fix this in Maid Hiring Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37744 — 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-37744 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