CVE-2024-42904
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 cross-site scripting (XSS) vulnerability in SysPass 3.2.x allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the name parameter at /Controllers/ClientController.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 · high confidenceA stored cross-site scripting (XSS) vulnerability exists in SysPass 3.2.x where the name parameter in /Controllers/ClientController.php is not properly sanitized before storage or rendering, allowing attackers to inject malicious HTML or JavaScript that executes in the context of other users' browsers.
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.2.0, <= 3.2.11CVSS 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.
-
Identify installed SysPass versionCheck the application version displayed in the SysPass admin interface (usually in the footer or About section) or check the version file in the installation directoryAffected if The installed version is >= 3.2.0 and <= 3.2.11
-
Locate ClientController.phpFind the ClientController.php file in the /Controllers/ directory of the SysPass installationAffected if The file exists and contains the 'name' parameter handling code without proper sanitization
-
Inspect the name parameter handling in ClientController.phpExamine the code that processes the 'name' parameter in ClientController.php, looking for input sanitization or validation functions applied before storageAffected if The 'name' parameter is processed and stored without proper input validation or escaping functions (such as htmlspecialchars, strip_tags, or context-specific encoding)
-
Check if client management feature is accessibleLog into SysPass as an authenticated user with access to client management and verify the ability to create or edit clientsAffected if The client management module is accessible and allows users to input or modify client names
You are affected if SysPass version is between 3.2.0 and 3.2.11 inclusive, ClientController.php processes the name parameter without proper sanitization, and the client management feature is accessible to users who can input data.
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.
dbcve · scopedImplement proper input validation and output encoding for the name parameter in ClientController.php. Apply context-appropriate escaping when rendering the client name field in all views.
SysPass 3.2.12 or latest stable 3.x release
- 1. Backup your current SysPass installation and database before making any changes.
- 2. Check the official SysPass GitHub repository (github.com/nuxsmin/sysPass) for the latest release.
- 3. Download the latest stable version of SysPass (version 3.2.12 or later, or the most recent 3.x release).
- 4. Follow the standard SysPass upgrade procedure: stop the web server, replace the application files, run any database migration scripts if required, then restart the web server.
- 5. Verify the upgrade was successful by logging into the SysPass administration panel.
- 6. Confirm the XSS vulnerability is remediated by attempting to inject a benign test script into the client name field at /Controllers/ClientController.php and verifying it is properly escaped or blocked.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42904 — 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-42904 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