CVE-2025-63441
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 · uneditedOpen Source Social Network (OSSN) 8.6 is vulnerable to Cross Site Scripting (XSS) via the parameter param` at endpoint u/administrator/friends.
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 confidenceOSSN 8.6 contains a reflected Cross Site Scripting (XSS) vulnerability in the administrator friends endpoint (u/administrator/friends). The 'param' parameter accepts unsanitized user input that gets rendered in the HTTP response without proper output encoding, allowing injection of arbitrary JavaScript code that executes in the context of authenticated administrator sessions.
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= 8.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 OSSN installation and versionLocate the OSSN installation directory and check version.php or similar version file. Alternatively, check the database version record if accessible.Affected if The installed version is exactly 8.6
-
Verify administrator friends endpoint existsCheck if the file path components/administrator/friends.php or the routed endpoint u/administrator/friends exists within the OSSN installation.Affected if The administrator friends endpoint exists and is accessible
-
Confirm administrator authentication is possibleCheck if administrator accounts can exist in the OSSN database (ossn_users table with admin role) and if the authentication system is enabled.Affected if Administrator accounts can be created and authenticated in the system
-
Test param parameter reflectionSubmit a request to the u/administrator/friends endpoint with a benign test string in the 'param' parameter (e.g., ?param=test123), then inspect the HTTP response to see if the value is reflected without encoding.Affected if The 'param' parameter value is reflected in the response without HTML encoding or sanitization
You are affected if running OSSN version 8.6 and the administrator friends endpoint reflects the 'param' parameter unencoded in responses.
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 contextual output encoding for the 'param' parameter before rendering in HTML, and add input validation to reject suspicious characters. Consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.
- 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-2025-63441 — 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-63441 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