CVE-2025-9567
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 · uneditedThe eHRD developed by Sunnet has a Reflected Cross-site Scripting vulnerability, allowing unauthenticated remote attackers to execute arbitrary JavaScript codes in user's browser through phishing attacks.
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 confidenceThe eHRD system developed by Sunnet contains a reflected cross-site scripting (XSS) vulnerability. Unauthenticated remote attackers can inject malicious JavaScript code into web pages viewed by users through specially crafted URLs, leveraging phishing attacks to trick users into clicking malicious links.
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 dataall versionsCVSS 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.
-
Confirm eHRD system presenceIdentify if Sun.net Ehrd Ctms is installed in your environment by reviewing deployed web applications, checking server directories for eHRD-related files, or searching for 'ehrd' or 'ctms' in your application inventoryAffected if The Sun.net Ehrd Ctms application is present and accessible on your network
-
Locate the web interface URLIdentify the base URL and endpoints where the eHRD system is accessible (commonly found in web server configuration files, reverse proxy settings, or application deployment manifests)Affected if The eHRD web interface is reachable via HTTP/HTTPS
-
Identify input parametersBrowse the application and catalog all URL parameters, form fields, and query strings used in requests (e.g., login pages, search functions, navigation parameters)Affected if The application accepts user-supplied parameters in URLs without proper validation
-
Test for reflected inputInject a harmless test string (such as <script>alert('XSS')</script> or a benign HTML tag) into URL parameters and observe if the input is reflected verbatim in the response page sourceAffected if User-supplied input appears unmodified in the HTML response, indicating lack of output encoding
-
Verify authentication is not requiredAttempt to access the vulnerable endpoint without logging in or providing credentials to confirm the XSS is reachable by unauthenticated usersAffected if The reflected input is returned to unauthenticated users without requiring authentication
If the Sun.net Ehrd Ctms system is deployed and URL parameters reflect unsanitized user input to unauthenticated users, your environment is affected by CVE-2025-9567.
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 user-supplied data, and deploy Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9567 — 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-2025-9567 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