Skip to main content
VulnerabilityPublished Updated

CVE-2024-37879: usvn · Cross-site Scripting

Affects usvnSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium : upgrade to 1.0.12 when convenient.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.12
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 2024

  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

Upgrade usvn/usvn to 1.0.12.

Affected software

ProductAffectedFixed in
GitHubusvn/usvnpkg:github/usvn/usvnOther threatsAffected
  • <1.0.12
Fixed in
  • 1.0.12

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

AI-suggested

  1. Upgrade USVN to version 1.0.12 or later immediately, as this version addresses the vulnerability.
  2. Implement strict input validation and sanitization on all administrative input fields, especially "siteTitle", "siteIco", and "siteLogo", to prevent injection of malicious code.
  3. Enforce the principle of least privilege by limiting administrator access only to trusted personnel and using multi-factor authentication to reduce the risk of credential compromise.
  4. Monitor administrative activities and audit logs for unusual or unauthorized configuration changes.
  5. Employ web application firewalls (WAFs) with rules designed to detect and block suspicious payloads targeting input fields.
  6. Educate administrators about phishing and social engineering risks to prevent credential theft.
  7. Regularly review and update security policies related to SVN management tools and conduct vulnerability assessments to detect similar issues proactively.

Description

Improper input validation in /admin/config/save in User-friendly SVN (USVN) before v1.0.12 and below allows administrators to execute arbitrary code via the fields "siteTitle", "siteIco" and "siteLogo".

References

Community reviews

Loading reviews…