LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15308: Support Incident Tracker (aka SiT!

Support Incident Tracker (aka SiT! or SiTracker) 3.67 p2 allows post-authentication SQL injection via the site_edit.php typeid or site parameter, the search_incidents_advanced.php search_title parameter, or the report_qbe.php criteriafield parameter.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-15308 is a post-login SQL injection issue in Support Incident Tracker, also called SiT! or SiTracker, version 3.67 p2. An authenticated user may be able to manipulate database queries through specific page parameters. The public sources do not provide a CVSS score, confirmed patch, or evidence of active exploitation.

Executive priority

Prioritize discovery and containment if SiT!/SiTracker is still in use. The vulnerability is old and post-authentication, but incident-tracking systems often hold sensitive data, making exposure meaningful even without confirmed active exploitation.

Technical view

The CVE describes post-authentication SQL injection in SiT!/SiTracker 3.67 p2 affecting parameters on site_edit.php, search_incidents_advanced.php, and report_qbe.php. The vulnerable inputs named are typeid, site, search_title, and criteriafield. Impact is not scored in the supplied sources, but SQL injection may affect confidentiality or integrity of incident-tracking data.

Likely exposure

Exposure is limited to organizations still running Support Incident Tracker/SiTracker 3.67 p2. Risk is higher where the application is internet-accessible, where many users have accounts, or where incident records contain sensitive operational, customer, or security data.

Exploitation context

The issue requires authentication according to the CVE description. The source bundle does not show CISA KEV listing, active exploitation, public weaponization status, or a vendor-confirmed fix. Treat exploitability as plausible but source evidence as incomplete.

Researcher notes

Source detail is sparse: no CVSS vector, no CWE mapping, no CPEs, and no confirmed remediation in the provided bundle. Validation should focus on version confirmation, reachable affected routes, role access, and logs rather than assumptions about broader product lines.

Mitigation direction

  • Inventory any Support Incident Tracker or SiTracker deployments and confirm versions.
  • Check current project or vendor guidance for fixed releases or official mitigation.
  • Restrict application access to trusted networks or VPN where operationally possible.
  • Remove unused accounts and limit access to users with a business need.
  • Monitor database and web logs for suspicious requests to the named endpoints.

Validation and detection

  • Confirm whether any deployment is running SiT!/SiTracker 3.67 p2.
  • Review access logs for site_edit.php, search_incidents_advanced.php, and report_qbe.php activity.
  • Identify which authenticated roles can reach the affected pages.
  • Use non-destructive staging tests to verify input handling after any upgrade or mitigation.
  • Check whether incident data includes credentials, customer data, or sensitive security details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-15308 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.