CVE-2024-40474
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 Reflected Cross Site Scripting (XSS) vulnerability was found in "edit-cate.php" in SourceCodester House Rental Management System v1.0.
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 confidenceReflected Cross Site Scripting (XSS) vulnerability in edit-cate.php of SourceCodester House Rental Management System v1.0 allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected back in the HTTP response without proper encoding.
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.
-
Confirm House Rental Management System v1.0 installationLocate the web application directory and check for files indicating this specific version (e.g., version file, about page, or admin dashboard showing version 1.0)Affected if The application is SourceCodester Mayurik Best House Rental Management System version 1.0
-
Locate edit-cate.php fileSearch the web root for edit-cate.php (commonly in /admin/, /category/, or root directories)Affected if The file edit-cate.php exists in the application web directory
-
Verify edit-cate.php is web-accessibleAttempt to access edit-cate.php via HTTP request (e.g., GET /edit-cate.php or similar path)Affected if The file responds to HTTP requests and is reachable without authentication or after authentication
-
Inspect code for unsanitized parameter reflectionOpen edit-cate.php in a text editor and examine how user-supplied parameters (typically GET/POST parameters like id, category, name) are handled - look for direct echoing of $_GET, $_POST, or $_REQUEST values without htmlspecialchars(), htmlentities(), or similar encoding functionsAffected if User-supplied parameters are echoed back in the HTTP response without HTML encoding (e.g., no htmlspecialchars() with ENT_QUOTES)
If edit-cate.php is present and reflects any user input without HTML encoding, the system is vulnerable to reflected XSS via CVE-2024-40474.
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/escaping on all user-supplied parameters in edit-cate.php before reflecting them in the response. Use context-appropriate encoding (HTML entity encoding) for the output context.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40474 — 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-2024-40474 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