LiveActive security incident?Get immediate response
CVE Record

CVE-2014-3119: Multiple SQL injection vulnerabilities in web2Project 3.1 and earlier allow remote authenticated users to e...

Multiple SQL injection vulnerabilities in web2Project 3.1 and earlier allow remote authenticated users to execute arbitrary SQL commands via the (1) search_string parameter in the contacts module to index.php or allow remote attackers to execute arbitrary SQL commands via the updatekey parameter to (2) do_updatecontact.php or (3) updatecontact.php.

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

Security readout for executives and security teams

Plain-English summary

CVE-2014-3119 is a set of SQL injection flaws in web2Project 3.1 and earlier. Attackers may be able to make the application run unintended database queries. That can threaten project, contact, user, or operational data if an exposed instance is still in use.

Executive priority

Treat this as a priority if web2Project is still deployed. The business concern is database compromise through an older project-management application, not broad internet-wide exposure proven by current sources.

Technical view

The CVE describes multiple SQL injection issues affecting the contacts module and contact update endpoints in web2Project 3.1 and earlier. One vector is authenticated; the CVE text also describes remote attacker vectors involving update contact functionality. The bundle does not include CVSS, CWE, or a named fixed release.

Likely exposure

Exposure is likely limited to organizations still running web2Project 3.1 or earlier, especially internet-facing or partner-accessible deployments. Confirm whether the application is still present, reachable, and connected to sensitive databases.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The CVE states arbitrary SQL execution is possible, but this analysis does not infer exploit availability beyond the cited advisory and commits.

Researcher notes

The CVE bundle provides affected version text and two upstream commits, but lacks CVSS, CWE, normalized CPEs, and a named patched release. Validate exposure through version and code review, then map commits to the deployed branch before closure.

Mitigation direction

  • Identify all web2Project deployments and versions.
  • Prioritize any web2Project 3.1 or earlier instance.
  • Review the HTBridge advisory and linked upstream commits.
  • Check current vendor or project guidance for fixed releases.
  • Restrict access while remediation is being planned.
  • Back up and monitor affected databases.

Validation and detection

  • Confirm whether web2Project exists in asset inventory.
  • Check application version against 3.1 and earlier.
  • Review web logs for unusual contact update activity.
  • Review database logs for unexpected queries.
  • Verify patched code includes referenced upstream changes.
  • Confirm exposed routes are no longer vulnerable after remediation.
Prepared
Confidence
medium
Sources
5

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-2014-3119 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
4Source 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.