LiveActive security incident?Get immediate response
CVE Record

CVE-2017-9463: The application Piwigo is affected by a SQL injection vulnerability in version 2.9.0 and possibly prior.

The application Piwigo is affected by a SQL injection vulnerability in version 2.9.0 and possibly prior. This vulnerability allows remote authenticated attackers to obtain information in the context of the user used by the application to retrieve data from the database. The user_list_backend.php component is affected: values of the iDisplayStart & iDisplayLength parameters are not sanitized; these are used to construct a SQL query and retrieve a list of registered users into the application.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Piwigo 2.9.0, and possibly earlier versions, had a SQL injection issue in a backend user-listing component. An authenticated remote user could influence pagination parameters and potentially read database information available to the application's database account. The sources do not show active exploitation or a CVSS score.

Executive priority

Prioritize remediation for any internet-facing or multi-user Piwigo deployment. The issue can expose database-backed user information, but available evidence shows authentication is required and does not confirm active exploitation.

Technical view

The issue is in user_list_backend.php. The iDisplayStart and iDisplayLength parameters were not sanitized before being used to build a SQL query for registered users. Impact is information disclosure through SQL injection within the permissions of the database user configured for the Piwigo application.

Likely exposure

Exposure is most likely where Piwigo 2.9.0 or possibly earlier versions are deployed and authenticated users can reach the affected user-list backend. Internet exposure raises concern, but authentication is required per the CVE description.

Exploitation context

The provided sources describe remote authenticated exploitation potential but do not cite active exploitation, public weaponization, or inclusion in CISA KEV. Treat this as a credible application-layer data exposure risk, not confirmed mass exploitation.

Researcher notes

The source bundle lacks CVSS, CWE, and precise fixed-version metadata. Analysis is grounded in the CVE description, the Piwigo issue, the upstream commit reference, and the Wizlynx advisory. Avoid assuming unauthenticated reachability or broader product impact.

Mitigation direction

  • Identify Piwigo deployments running version 2.9.0 or possibly earlier.
  • Review and apply the upstream Piwigo fix referenced by the project commit.
  • Check current Piwigo vendor guidance for the fixed release path.
  • Restrict access to authenticated administrative or user-management functions where possible.
  • Ensure the Piwigo database account has only required privileges.

Validation and detection

  • Inventory exposed Piwigo instances and confirm their running versions.
  • Verify user_list_backend.php includes input sanitization for pagination parameters.
  • Review application logs for unusual authenticated access to user-listing functions.
  • Review database logs for abnormal queries from the Piwigo application account.
  • Confirm remediation through vendor release notes or the referenced upstream commit.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2017-9463 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
4Source links

CVSS and timeline data

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

Source materials

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.