LiveActive security incident?Get immediate response
CVE Record

CVE-2018-18251: Deltek Vision 7.x before 7.6 permits the execution of any attacker supplied SQL statement through a custom...

Deltek Vision 7.x before 7.6 permits the execution of any attacker supplied SQL statement through a custom RPC over HTTP protocol. The Vision system relies on the client binary to enforce security rules and integrity of SQL statements and other content being sent to the server. Client HTTP calls can be manipulated by one of several means to execute arbitrary SQL statements (similar to SQLi) or possibly have unspecified other impact via this custom protocol. To perform these attacks an authenticated session is first required. In some cases client calls are obfuscated by encryption, which can be bypassed due to hard-coded keys and an insecure key rotation protocol. Impacts may include remote code execution in some deployments; however, the vendor states that this cannot occur when the installation documentation is heeded.

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

Security readout for executives and security teams

Plain-English summary

CVE-2018-18251 affects Deltek Vision 7.x before 7.6. An authenticated attacker could manipulate client-to-server HTTP calls so the server accepts attacker-supplied SQL instead of relying on trusted server-side checks. This can threaten business data integrity and confidentiality, and sources note possible remote code execution in some deployments.

Executive priority

Treat this as a high-priority application risk if Deltek Vision is present. The business concern is not just outage; it is unauthorized data access, data manipulation, and possible deeper compromise in misconfigured deployments.

Technical view

The issue is in a custom RPC-over-HTTP protocol where Vision relies on the client binary to enforce SQL and content integrity. Authenticated sessions can manipulate client HTTP calls to execute arbitrary SQL-like statements. Some calls are obfuscated, but the source says hard-coded keys and insecure key rotation can bypass that protection.

Likely exposure

Exposure is likely limited to organizations running Deltek Vision 7.x before 7.6. The source bundle does not identify CPEs, deployment prevalence, or internet exposure. Risk increases where authenticated users can reach the Vision HTTP interface and where installation guidance was not followed.

Exploitation context

The CVE description says authentication is required. It does not state public exploitation, and CISA KEV status in the bundle is false. The advisory evidence is enough to treat this as serious because arbitrary SQL can affect sensitive project, financial, and customer data.

Researcher notes

Evidence is centered on the CVE description and referenced advisory. No CVSS, CWE, CPE, exploit-in-the-wild, or detailed vendor fix data is present in the supplied bundle. Avoid assuming unauthenticated access or active exploitation without additional sources.

Mitigation direction

  • Inventory Deltek Vision deployments and identify any 7.x versions before 7.6.
  • Check Deltek/vendor guidance and apply the supported update or remediation path.
  • Review installation documentation, especially controls related to remote code execution risk.
  • Limit access to Vision HTTP interfaces to trusted users and networks.
  • Audit affected systems for suspicious database or application activity.

Validation and detection

  • Confirm product name and version on each Deltek Vision deployment.
  • Verify whether any instance is earlier than version 7.6.
  • Review access paths to the custom RPC-over-HTTP interface.
  • Check whether installation documentation was followed for server hardening.
  • Look for unusual authenticated database activity during the exposure window.
Prepared
Confidence
medium
Sources
3

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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2018-18251 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
2Source 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.