CVE-2024-48170
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 · uneditedPHPGurukul Small CRM 3.0 is vulnerable to Cross Site Scripting (XSS) via a crafted payload injected into the name in the profile.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 confidencePHPGurukul Small CRM 3.0 contains a stored Cross Site Scripting (XSS) vulnerability in the profile.php component where user-supplied input to the 'name' field is not properly sanitized before being stored and rendered to other users, allowing injection of arbitrary JavaScript code.
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= 3.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 the Small CRM versionLocate the version identifier in the application source code, typically found in a version file, README, or footer/includes of the application. Compare it to the affected version 3.0.Affected if The installed version is 3.0 exactly.
-
Verify profile.php existsLocate the profile.php file in the web application directory structure. This is the component where the vulnerability exists.Affected if profile.php is present in the application root or user directory.
-
Confirm user profile functionality is activeCheck if user registration or profile management features are enabled and accessible in the application. The XSS can only be triggered when users can create or edit their profiles.Affected if Users can register or access profile editing functionality.
-
Inspect name field handling in profile.phpExamine the profile.php source code where the 'name' field is processed. Look for the code that handles saving user input to the name field and code that displays the name back to users.Affected if The name field is processed and stored without server-side sanitization (such as htmlspecialchars, strip_tags, or other encoding functions), and it is rendered back to users without output encoding.
-
Test for XSS in name fieldIf you have access to the application, create a test user or edit an existing profile. In the name field, input a benign XSS test payload such as <script>alert('XSS')</script> or <img src=x onerror=alert('XSS')>. Save the profile, then view the profile page or any area where the name is displayed.Affected if The JavaScript payload executes or is rendered unescaped in the browser when the name is displayed.
You are affected if you are running Small CRM version 3.0, profile.php is accessible, users can manage profiles, and the name field input is not sanitized before storage or output.
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 server-side input validation and output encoding/HTML escaping when displaying the name field in profile.php to prevent script execution; also review and fix similar input fields throughout the application for persistent XSS vulnerabilities.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48170 — 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-48170 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