<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: best software</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2004-1611: SalesLogix 6.1 does not verify if a user is authenticated before performing sensitive operations, which could </title><link>https://patchthecve.com/cve/CVE-2004-1611.html</link><guid>https://patchthecve.com/cve/CVE-2004-1611.html</guid><pubDate>Tue, 16 Jun 2026 22:08:02 +0000</pubDate><description>MEDIUM 5.1: SalesLogix 6.1 does not verify if a user is authenticated before performing sensitive operations, which could allow remote attackers to (1) execute arbitrary SLX commands on the server or spoof the server via a man-in-the-middle (MITM) attack, or (2) obtain the database password via a GetConnection </description></item><item><title>CVE-2004-1610: SalesLogix 6.1 uses client-specified pathnames for writing certain files, which might allow remote authenticat</title><link>https://patchthecve.com/cve/CVE-2004-1610.html</link><guid>https://patchthecve.com/cve/CVE-2004-1610.html</guid><pubDate>Tue, 16 Jun 2026 22:08:02 +0000</pubDate><description>HIGH 7.5: SalesLogix 6.1 uses client-specified pathnames for writing certain files, which might allow remote authenticated users to create arbitrary files and execute code via the (1) vMME.AttachmentPath or (2) vMME.LibraryPath variables.</description></item><item><title>CVE-2004-1609: SalesLogix 6.1 includes usernames, passwords, and other sensitive information in the headers of an HTTP respon</title><link>https://patchthecve.com/cve/CVE-2004-1609.html</link><guid>https://patchthecve.com/cve/CVE-2004-1609.html</guid><pubDate>Tue, 16 Jun 2026 22:08:02 +0000</pubDate><description>MEDIUM 5.0: SalesLogix 6.1 includes usernames, passwords, and other sensitive information in the headers of an HTTP response, which could allow remote attackers to gain access.</description></item><item><title>CVE-2004-1608: SQL injection vulnerability in SalesLogix 6.1 allows remote attackers to execute arbitrary SQL statements via </title><link>https://patchthecve.com/cve/CVE-2004-1608.html</link><guid>https://patchthecve.com/cve/CVE-2004-1608.html</guid><pubDate>Tue, 16 Jun 2026 22:08:02 +0000</pubDate><description>HIGH 7.5: SQL injection vulnerability in SalesLogix 6.1 allows remote attackers to execute arbitrary SQL statements via the id parameter in a view operation.</description></item><item><title>CVE-2004-1607: slxweb.dll in SalesLogix 6.1 allows remote attackers to obtain sensitive information via a (1) Library or (2) </title><link>https://patchthecve.com/cve/CVE-2004-1607.html</link><guid>https://patchthecve.com/cve/CVE-2004-1607.html</guid><pubDate>Tue, 16 Jun 2026 22:08:02 +0000</pubDate><description>MEDIUM 5.0: slxweb.dll in SalesLogix 6.1 allows remote attackers to obtain sensitive information via a (1) Library or (2) Attachment request with an invalid file parameter, which reveals the path in an error message.</description></item><item><title>CVE-2004-1606: slxweb.dll in SalesLogix 6.1 allows remote attackers to cause a denial service (application crash) via an inva</title><link>https://patchthecve.com/cve/CVE-2004-1606.html</link><guid>https://patchthecve.com/cve/CVE-2004-1606.html</guid><pubDate>Tue, 16 Jun 2026 22:08:02 +0000</pubDate><description>MEDIUM 6.4: slxweb.dll in SalesLogix 6.1 allows remote attackers to cause a denial service (application crash) via an invalid HTTP request, which might also leak sensitive information in the ErrorLogMsg cookie.</description></item><item><title>CVE-2004-1605: SalesLogix 6.1 allows remote attackers to bypass authentication by modifying the slxweb cookie to set user=Adm</title><link>https://patchthecve.com/cve/CVE-2004-1605.html</link><guid>https://patchthecve.com/cve/CVE-2004-1605.html</guid><pubDate>Tue, 16 Jun 2026 22:08:01 +0000</pubDate><description>HIGH 7.5: SalesLogix 6.1 allows remote attackers to bypass authentication by modifying the slxweb cookie to set user=Admin, teams=ADMIN!, and usertype=Administrator.</description></item></channel></rss>