LiveActive security incident?Get immediate response
CVE Record

CVE-2018-1000630: Battelle V2I Hub 2.5.1 is vulnerable to SQL injection.

Battelle V2I Hub 2.5.1 is vulnerable to SQL injection. A remote authenticated attacker could send specially-crafted SQL statements to /api/PluginStatusActions.php and /status/pluginStatus.php using the jtSorting or id parameter, which could allow the attacker to view, add, modify or delete information in the back-end database.

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-1000630 is an authenticated SQL injection issue in Battelle V2I Hub 2.5.1. If an attacker already has valid access, they may be able to manipulate database-backed status/API requests and read or change back-end database data. The source bundle does not provide a CVSS score or named patch.

Executive priority

Treat this as high priority if Battelle V2I Hub 2.5.1 is deployed. The issue could affect database confidentiality and integrity, but public sources do not confirm active exploitation or a specific patch. Prioritize inventory confirmation and vendor-guided remediation.

Technical view

The CVE description identifies SQL injection in /api/PluginStatusActions.php and /status/pluginStatus.php through the jtSorting or id parameter. The described impact is unauthorized viewing, adding, modifying, or deleting database information by a remote authenticated attacker. No CWE, CVSS vector, or affected CPE is provided in the bundle.

Likely exposure

Exposure is limited to environments running Battelle V2I Hub 2.5.1 where authenticated users can reach the affected PHP endpoints. The bundle’s structured affected-product fields are incomplete, so confirm deployments by asset inventory rather than CPE matching alone.

Exploitation context

The source bundle does not indicate known active exploitation, and KEV is false. The attack requires authentication according to the CVE description. Public evidence provided is limited to the CVE record and IBM X-Force reference.

Researcher notes

The record is sparse: no CVSS, CWE, CPE, exploit confirmation, or patch details are included. The strongest technical evidence is the CVE description naming two endpoints, two parameters, authenticated remote attack context, and database read/write/delete impact.

Mitigation direction

  • Identify any Battelle V2I Hub 2.5.1 deployments.
  • Check vendor or IBM X-Force guidance for supported fixes.
  • Restrict access to the affected application and endpoints.
  • Review authenticated account access for least privilege.
  • Monitor application and database logs for suspicious activity.

Validation and detection

  • Confirm application version from asset inventory or host records.
  • Verify whether the two named PHP endpoints are reachable.
  • Review logs for unusual authenticated requests to those endpoints.
  • Check database audit logs for unexpected data changes.
  • Document compensating controls if no vendor fix is available.
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

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-2018-1000630 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.