CVE Tools

CVE-2017-20276

Joomla! Component SIMGenealogy 2.1.5 SQL Injection

No known exploitation. EPSS puts it in the 35th percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • Simbunch SIMGenealogyAffected: 2.1.5Upgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether your Joomla! site has SIMGenealogy installed and whether its version is 2.1.5.
  2. If it is version 2.1.5, remove or disable the component until your vendor provides a verified fixed release.
  3. There is no confirmed fixed version available; ask the component vendor for its replacement or remediation guidance.
  4. Review website and database access records for unusual requests to the component, especially requests containing unexpected database-query text.

What it is

From the CVE record

Joomla! Component SIMGenealogy 2.1.5 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the type parameter. Attackers can send GET requests to index.php with the option=com_simgenealogy, view=latest parameters and inject malicious SQL in the type parameter to extract sensitive database information.

In plain language

Written by AI from the record

SIMGenealogy 2.1.5 has a flaw that can let an outsider steal website database information, so small businesses using that version should act now.

Unauthenticated SQL injection in SIMGenealogy 2.1.5 allows database-query manipulation through an HTTP GET request’s `type` parameter.

If you're affected

  • Website database data theft
  • Customer record exposure
  • Sensitive information disclosure

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS35th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 35th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

5 events over 61 days, from the signal feeds we watch.

  1. Record updated
  2. Record updated
  3. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Scored 8.2 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for SIMGenealogy, not every advisory.