LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40927: Online Leave Management System v1.0 is vulnerable to SQL Injection via /leave_system/classes/Master.php?f=d...

Online Leave Management System v1.0 is vulnerable to SQL Injection via /leave_system/classes/Master.php?f=delete_designation.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes a SQL injection flaw in Online Leave Management System v1.0. A highly privileged authenticated user could potentially manipulate database queries through the delete_designation function, risking data disclosure, modification, or disruption. The source bundle does not identify a vendor patch or active exploitation.

Executive priority

Treat as a high-priority issue if this leave management system is deployed, especially if admin access is internet-accessible. Prioritize inventory, access restriction, and vendor guidance because no patch information is provided in the source bundle.

Technical view

CVE-2022-40927 is CWE-89 SQL injection in /leave_system/classes/Master.php?f=delete_designation. CVSS 3.1 is 7.2, with network access, low complexity, high privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to deployments of Online Leave Management System v1.0 where the affected endpoint is reachable by authenticated high-privilege users. The CVE record does not provide CPEs, vendor metadata, or broader affected-version details.

Exploitation context

The provided sources include a public vulnerability report, but the bundle marks KEV as false and provides no evidence of active exploitation. High privileges are required, reducing opportunistic risk but increasing insider or compromised-admin account impact.

Researcher notes

Evidence is sparse: affected vendor/product fields are n/a, and the CVE record mainly identifies the endpoint and vulnerability type. Avoid assuming other versions are affected. Validation should focus on confirmed v1.0 deployments and code review rather than exploit reproduction.

Mitigation direction

  • Check the project or vendor guidance for any fixed release or advisory.
  • Restrict administrative access to trusted networks and accounts.
  • Review affected code for parameterized queries around delete_designation handling.
  • Apply least privilege to the application database account.
  • Monitor logs for unusual designation deletion or SQL error activity.

Validation and detection

  • Inventory any Online Leave Management System v1.0 deployments.
  • Confirm whether /leave_system/classes/Master.php is present and reachable.
  • Verify administrative roles are tightly controlled and audited.
  • Review application code for unsafe SQL construction in delete_designation.
  • Check database and application logs for anomalous admin activity.
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.

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-2022-40927 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
7.2 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-40927Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
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.