Skip to main content
VulnerabilityPublished Updated

CVE-2025-63585: opensource-socialnetwork · SQL Injection

Affects opensource-socialnetworkSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubopensource-socialnetwork/opensource-socialnetworkpkg:github/opensource-socialnetwork/opensource-socialnetworkOther threatsAffected
  • =8.6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-63585, organizations should implement strict input validation and sanitization on the timestamp parameter to prevent injection of malicious SQL code. Employing parameterized queries or prepared statements in the backend database interactions is critical to eliminate SQL Injection risks. Since no official patches are currently available, applying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the /action/rtcomments/status endpoint can provide interim protection. Regularly audit and monitor database logs for unusual query patterns or access anomalies. Organizations should also review and restrict database user privileges to minimize potential damage from successful injections. Finally, maintain awareness of OSSN updates and apply official patches promptly once released. Conducting security assessments and penetration testing focused on injection flaws will help identify and remediate similar vulnerabilities proactively.

Description

OSSN (Open Source Social Network) 8.6 is vulnerable to SQL Injection in /action/rtcomments/status via the timestamp parameter.

References

Community reviews

Loading reviews…