LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31383: Directory Management System v1.0 was discovered to contain a SQL injection vulnerability via the editid par...

Directory Management System v1.0 was discovered to contain a SQL injection vulnerability via the editid parameter in view-directory.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-31383 is a reported SQL injection in Directory Management System v1.0. The issue is tied to the editid parameter in view-directory.php. If an exposed instance is vulnerable, attackers may be able to interfere with database queries. The public record does not provide severity scoring, vendor CPEs, authentication context, or confirmed remediation.

Executive priority

Prioritize confirmation of exposure. If the product is internet-facing, treat remediation as time-sensitive because SQL injection can affect sensitive directory data and database integrity, even though severity is not scored.

Technical view

The CVE record describes SQL injection through the editid parameter of view-directory.php in Directory Management System v1.0. The source bundle includes a public PoC reference, but no CVSS vector, CWE mapping, patch advisory, or normalized affected product metadata. Exposure assessment depends on confirming the exact application and route in the environment.

Likely exposure

Likely limited to organizations running Directory Management System v1.0 with view-directory.php reachable. The source data does not identify vendor, CPE, deployment model, or whether authentication is required.

Exploitation context

The CVE is not listed as CISA KEV in the supplied data. A public GitHub PoC reference exists, but the provided sources do not establish active exploitation in the wild.

Researcher notes

Evidence is sparse. The core claim is SQL injection via editid in view-directory.php. Do not assume exploitability, authentication status, database impact, or patch availability without validating against the specific deployed codebase.

Mitigation direction

  • Identify whether Directory Management System v1.0 is deployed.
  • Check vendor or project guidance for an official patch.
  • Restrict access to view-directory.php if the application remains in use.
  • Review database query handling for editid and use parameterized queries.
  • Monitor logs for unusual requests to view-directory.php.

Validation and detection

  • Inventory public and internal web apps for Directory Management System v1.0.
  • Confirm whether view-directory.php exists and accepts editid.
  • Review server-side code for unsafe SQL construction using editid.
  • Check security logs for suspicious access to the affected route.
  • Document whether a vendor fix or local code fix is applied.
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-2022-31383 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
3Timeline events
1ADP providers
2Source links

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.

ADP provider summaries

CVECVE Program Container
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.