LiveActive security incident?Get immediate response
CVE Record

CVE-2019-16693: phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/order.php table parameter when action=add...

phpIPAM 1.4 allows SQL injection via the app/admin/custom-fields/order.php table parameter when action=add is used.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-16693 is a reported SQL injection issue in phpIPAM 1.4. The vulnerable input is the table parameter in an administrative custom-fields ordering endpoint when action=add is used. SQL injection can expose or alter application database data, but the source bundle does not provide CVSS scoring, patch details, or confirmed exploitation.

Executive priority

Treat this as a targeted exposure check, not a confirmed emergency from the provided evidence. If phpIPAM 1.4 is present, prioritize remediation because SQL injection can affect sensitive IPAM data and infrastructure records.

Technical view

The CVE description identifies SQL injection in app/admin/custom-fields/order.php through the table parameter when action=add. Public references include a GitHub issue and a PoC-style write-up. The provided data does not establish authentication requirements, exploit prevalence, fixed versions, or exact impact beyond SQL injection in phpIPAM 1.4.

Likely exposure

Exposure is likely limited to organizations running phpIPAM 1.4, especially where administrative phpIPAM interfaces are reachable by broad internal networks or the internet. The bundle’s structured affected field is incomplete, so confirm product and version locally.

Exploitation context

The CVE is not listed as KEV in the provided bundle. A public PoC-style reference exists, but the sources supplied do not prove active exploitation, weaponization in the wild, or a known automated campaign.

Researcher notes

The source bundle is sparse: no CVSS, CWE, fixed version, authentication requirement, or complete affected-product metadata is provided. Analysis should remain bounded to phpIPAM 1.4 and the named endpoint unless additional vendor or NVD data is reviewed.

Mitigation direction

  • Inventory all phpIPAM deployments and identify any running version 1.4.
  • Check phpIPAM vendor guidance and issue history for fixed versions or official workarounds.
  • Restrict phpIPAM administrative access to trusted networks and authorized users only.
  • Prioritize upgrade or remediation once a vendor-supported path is confirmed.
  • Review database and application logs for suspicious administrative custom-field activity.

Validation and detection

  • Confirm whether phpIPAM 1.4 is deployed in production or staging.
  • Check whether app/admin/custom-fields/order.php is present and reachable.
  • Review web logs for requests to that path with action=add.
  • Verify administrative interfaces are not internet-exposed unless explicitly required.
  • Document remediation status and evidence against vendor guidance.
Prepared
Confidence
medium
Sources
4

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-2019-16693 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
3Source 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.