CVE-2007-5635

CVE-2007-5635 is a critical-severity vulnerability in Sitracker Support Incident Tracker with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

• Severity: Critical (CVSS 2.0 base score 10.0)
• EPSS exploit prediction: 1% (70th percentile)
• Actively exploited: Not listed in CISA KEV
• Affected product: Sitracker Support Incident Tracker
• Published: 2007-10-23
• Last modified: 2026-06-16

Description

Multiple unspecified vulnerabilities in Salford Software Support Incident Tracker (SiT!) before 3.30 have unknown impact and attack vectors.

Frequently asked questions

What is CVE-2007-5635?

Multiple unspecified vulnerabilities in Salford Software Support Incident Tracker (SiT!) before 3.30 have unknown impact and attack vectors.

How severe is CVE-2007-5635?

CVE-2007-5635 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2007-5635 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2007-5635?

CVE-2007-5635 primarily affects Sitracker Support Incident Tracker. In total, 44 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2007-5635?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2007-5635 published?

CVE-2007-5635 was published on 2007-10-23 and last updated on 2026-06-16.

References

• http://secunia.com/advisories/27226
• http://sourceforge.net/project/shownotes.php?release_id=547027
• http://www.securityfocus.com/bid/26151

Affected products (44)

• cpe:2.3:a:sitracker:support_incident_tracker:*:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:1.8.00:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:2.8.00:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.00:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.00:beta1:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.00:beta2:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.00:beta3:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.01:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.02:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.03:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.03a:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.04a:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.05:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.06:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.07:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.07.1:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.07.2:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.07.3:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.08:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.08.1:alpha:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.09:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.10:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.11:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.12:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.14:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.15:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.16:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.17:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.18:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.19:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.20:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.21:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.22:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.22pl1:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.23:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.24:beta-2:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:3.24:beta2:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:10.8.00:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:11.8.00:*:*:*:*:*:*:*
• cpe:2.3:a:sitracker:support_incident_tracker:14.8.00:*:*:*:*:*:*:*

More vulnerabilities in Sitracker Support Incident Tracker

• CVE-2011-5072 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in Support Incident Tracker (aka SiT!) before 3.65 allow remote attackers to…
• CVE-2011-4337 — High (CVSS 7.5): Static code injection vulnerability in translate.php in Support Incident Tracker (aka SiT!) 3.45 through 3.65 allows…
• CVE-2011-5071 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in Support Incident Tracker (aka SiT!) before 3.64 allow remote attackers to…
• CVE-2011-3831 — High (CVSS 7.5): SQL injection vulnerability in incident_attachments.php in Support Incident Tracker (aka SiT!) 3.65 allows remote…
• CVE-2011-5074 — Medium (CVSS 6.8): Multiple cross-site request forgery (CSRF) vulnerabilities in Support Incident Tracker (aka SiT!) before 3.65 allow…
• CVE-2011-5068 — Medium (CVSS 6.8): Multiple cross-site request forgery (CSRF) vulnerabilities in Support Incident Tracker (aka SiT!) 3.65 allow remote…

All CVEs affecting Sitracker Support Incident Tracker →