Site Server Commerce vulnerabilitiesRanked by how likely they are to be used.
Site Server Commerce is made by Microsoft. We track 8 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Site Server Commerce, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Site Server Commerce vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Site Server Commerce's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Site Server Commerce flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 80%CVE-2000-0246Medium
IIS 4.0 and 5.0 does not properly perform ISAPI extension processing if a virtual directory is mapped to a UNC share, which allows remote attackers to read the source code of ASP and other files, aka the "Virtualized...
- 35%CVE-2000-0025Medium
IIS 4.0 and Site Server 3.0 allow remote attackers to read source code for ASP files if the file is in a virtual directory whose name includes extensions such as .com, .exe, .sh, .cgi, or .dll, aka the "Virtual...
- 15%CVE-2002-2081Medium
cphost.dll in Microsoft Site Server 3.0 allows remote attackers to cause a denial of service (disk consumption) via an HTTP POST of a file with a long TargetURL parameter, which causes Site Server to abort and leaves...
- 13%CVE-2002-2073Medium
Cross-site scripting (XSS) vulnerability in the default ASP pages on Microsoft Site Server 3.0 on Windows NT 4.0 allows remote attackers to inject arbitrary web script or HTML via the (1) ctr parameter in Default.asp...
- 12%CVE-2000-0024Medium
IIS does not properly canonicalize URLs, potentially allowing remote attackers to bypass access restrictions in third-party software via escape characters, aka the "Escape Character Parsing" vulnerability.
- 12%CVE-2002-1769High
Microsoft Site Server 3.0 prior to SP4 installs a default user, LDAP_Anonymous, with a default password of LdapPassword_1, which allows remote attackers the "Log on locally" privilege.
- 5.8%CVE-1999-0910Medium
Microsoft Site Server and Commercial Internet System (MCIS) do not set an expiration for a cookie, which could then be cached by a proxy and inadvertently used by a different user.
- 3.2%
Race condition in the SSL ISAPI filter in IIS and other servers may leak information in plaintext.
Running Site Server Commerce? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
IIS 4.0 and 5.0 does not properly perform ISAPI extension processing if a virtual directory is mapped to a UNC share, which allows remote attackers to read the source code of ASP and other files, aka the "Virtualized UNC Share" vulnerability.
- Matched to
- Site Server Commerce on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Site Server Commerce, across 1 version.
None of Site Server Commerce's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Site Server Commerce. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.