Security readout for executives and security teams
Plain-English summary
Maintenance Connection 2021 and 2022.2 are reported to have a SQL injection issue in the E-Mail to Work Order function. That type of flaw can expose or alter database-backed business records, but the supplied sources do not provide severity, CVSS, exploitability, or fix details.
Executive priority
Treat this as a targeted business application risk requiring prompt validation, not as a confirmed emergency. Prioritize asset identification and vendor confirmation because severity and fix details are missing from the provided sources.
Technical view
CVE-2022-46501 describes SQL injection via the E-Mail to Work Order function in Accruent LLC Maintenance Connection 2021 and 2022.2. The CVE metadata lacks CVSS, CWE classification, detailed affected CPEs, and remediation information. KEV is false in the provided bundle.
Likely exposure
Likely exposure is limited to organizations running Maintenance Connection 2021 or 2022.2, especially where E-Mail to Work Order is enabled. The affected-product metadata is incomplete, so confirm exact build and deployment details with Accruent records.
Exploitation context
The provided sources do not establish active exploitation. The CVE is not marked KEV in the bundle. A referenced public article describes a zero-day flaw, but the supplied data does not include exploit evidence or technical attack details.
Researcher notes
The record is sparse: no CVSS, CWE, CPEs, proof details, or remediation text are present. Analysis should stay anchored to the named function and versions. Avoid assuming broader Accruent product exposure without vendor confirmation.
Mitigation direction
Check Accruent guidance for fixed versions or supported workarounds.
Inventory Maintenance Connection instances and identify 2021 or 2022.2 deployments.
Assess whether E-Mail to Work Order can be disabled or isolated temporarily.
Restrict access paths to the affected function where operationally feasible.
Increase monitoring of application and database error logs.
Validation and detection
Confirm installed Maintenance Connection version and patch level.
Verify whether E-Mail to Work Order is enabled in each environment.
Review vendor advisories or support tickets for remediation status.
Check logs for abnormal database errors tied to that function.
Document compensating controls if no vendor fix is available.
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.
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
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 2, 2023, 00:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.