LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20254: Joomla! Component User Bench 1.0 SQL Injection via userid

Joomla! Component User Bench 1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the userid parameter. Attackers can send GET requests to index.php with the option=com_userbench&view=detail&userid parameter containing SQL injection payloads to extract sensitive database information including credentials and configuration data.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's Takehigh

Analyst readout for executives and security teams

Plain-English summary

A Joomla extension called User Bench version 1.0 has an unauthenticated SQL injection flaw. A remote attacker could query the site database and potentially expose credentials or configuration data. This matters most for organizations still running this old component on public Joomla sites.

Executive priority

Prioritize remediation for any public Joomla site using User Bench 1.0. The issue can expose sensitive database information without login, and public exploit information increases operational risk.

Technical view

CVE-2017-20254 is a CWE-89 SQL injection in Gegabyte User Bench 1.0 for Joomla. The reported vulnerable input is the userid parameter in the component’s detail view. The CVSS 4.0 score is 8.8, reflecting network access, low complexity, no privileges, and high confidentiality impact.

Likely exposure

Exposure is limited to Joomla sites with Gegabyte User Bench 1.0 installed, especially internet-facing sites. The provided sources do not confirm other versions, current maintenance status, or a vendor patch.

Exploitation context

A public ExploitDB reference exists, so proof-of-concept or exploit information is publicly available. The source bundle does not show CISA KEV listing or confirmed active exploitation in the wild.

Researcher notes

The record identifies User Bench 1.0 only. No safe fixed version is named in the provided sources. Treat remediation guidance as vendor-check, disable, or remove unless authoritative update information is found.

Mitigation direction

  • Inventory Joomla sites for the User Bench component and version 1.0.
  • If present, remove or disable the component if it is not business-critical.
  • Check vendor or Joomla extension guidance for an updated fixed release.
  • Restrict public access to affected component paths where feasible.
  • Review database and application logs for suspicious access to the component.

Validation and detection

  • Confirm whether User Bench is installed on each Joomla instance.
  • Verify the installed component version from Joomla administration or extension records.
  • Check web logs for requests targeting the User Bench detail view and userid input.
  • Review database user privileges used by the Joomla application.
  • Confirm compensating controls do not break required site functionality.
Prepared
Confidence
medium
Sources
6

Based on public source material and reviewed before publication.

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-2017-20254 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
High
CVSS
8.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

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.

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

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NVulnCheck
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.8High
CVSS 4.0 vector shape for CVE-2017-20254Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GegabyteUser Bench1.0Listed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.