VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

sscms: vulnerability history, versions and safety

sscms is a package in the NuGet ecosystem. Vulert records 5 vulnerabilities for it across 23 releases, from May 2022 to May 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 M3
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sscms vulnerabilities

Vulert verdict on sscms 7.4.0 i

Updated on 23 Oct 2026

Careful: 7.4.0 has 4 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 7.4.0 — affected i
  • Vulnerabilities on record 5 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2023 i
  • Highest CVSS 8.8 i
  • With no published fix 4 i
  • Stars 3,915 i
  • OpenSSF scorecard 1/10 i
  • Last release 13 months ago i
  • Licence AGPL-3.0-or-later i

Version list, release dates, licence and dependants published by NuGet, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for sscms, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.4.0 08 Sep 2025 H1 M3 AGPL-3.0-or-later No Details →
7.3.1 02 Aug 2024 H1 M3 AGPL-3.0-or-later No Details →
7.3.0 19 Feb 2024 H1 M3 AGPL-3.0-or-later No Details →
7.2.2 18 Sep 2023 H1 M3 AGPL-3.0-or-later No Details →
7.2.1 13 May 2023 M1 AGPL-3.0-or-later No Details →
7.2.0 26 Dec 2022 M1 AGPL-3.0-or-later No Details →
7.1.3 11 Aug 2022 M1 AGPL-3.0-or-later No Details →
7.1.2 04 May 2022 M1 AGPL-3.0-or-later No Details →
7.1.1 13 Mar 2022 M1 AGPL-3.0-or-later No Details →
7.1.0 14 Nov 2021 M1 AGPL-3.0-or-later No Details →
7.0.12 16 Jun 2021 M1 AGPL-3.0-or-later No Details →
7.0.10 18 Jan 2021 M1 AGPL-3.0-or-later No Details →
7.0.9 27 Dec 2020 M1 AGPL-3.0-or-later No Details →
7.0.8 20 Dec 2020 M1 AGPL-3.0-or-later No Details →
7.0.7 29 Nov 2020 M1 AGPL-3.0-or-later No Details →
7.0.6 05 Nov 2020 M1 AGPL-3.0-or-later No Details →
7.0.5 01 Nov 2020 M1 AGPL-3.0-or-later No Details →
7.0.4 27 Oct 2020 M1 AGPL-3.0-or-later No Details →
7.0.3 19 Oct 2020 M1 GPL-3.0-or-later No Details →
7.0.2 27 Sep 2020 M1 GPL-3.0-or-later No Details →
7.0.1 11 Sep 2020 M1 GPL-3.0-or-later No Details →
7.0.0 22 Aug 2020 M1 GPL-3.0-or-later No Details →
1.0.0-preview4 20 Mar 2020 H2 M2 — No Details →

All 23 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for sscms

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-42655: SQL Injection in SiteServer CMS 8.8 high No fix published 25 May 2022
CVE-2019-11401: SiteServer CMS RCE via unsafe file upload 7.2 high 6.12 24 May 2022
CVE-2022-30349: Cross Site Scripting in SSCMS 6.1 medium No fix published 03 Jun 2022
CVE-2023-2862: SSCMS vulnerable to Cross Site Scripting 6.1 medium No fix published 24 May 2023
CVE-2021-42656: Cross Site Scripting in SiteServer CMS 5.4 medium No fix published 25 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About sscms

Is sscms safe to use?

Vulert records 5 vulnerabilities for sscms in NuGet: 0 critical, 2 high, 3 medium and 0 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is sscms's Vulert package health score?

Vulert scores sscms 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of sscms affected?

Yes. 7.4.0, the version you would install today, has 4 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of sscms should I use?

7.4.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does sscms have?

5 vulnerabilities are recorded for sscms in the NuGet ecosystem: 0 critical, 2 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sscms vulnerabilities disclosed?

0 vulnerabilities were recorded for sscms in the last 12 months, and the oldest entry in this database dates to 24 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sscms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor sscms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sscms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.