CVE-2014-3040
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site request forgery (CSRF) vulnerability in IBM Emptoris Contract Management 9.5.x before 9.5.0.6 iFix 10, 10.0.0.x before 10.0.0.1 iFix 10, 10.0.1.x before 10.0.1.4, and 10.0.2.x before 10.0.2.2 iFix 2; Emptoris Sourcing Portfolio 9.5.x before 9.5.1.3, 10.0.0.x before 10.0.0.1, 10.0.1.x before 10.0.1.3, and 10.0.2.x before 10.0.2.4; and Emptoris Spend Analysis 9.5.x before 9.5.0.4, 10.0.1.x before 10.0.1.3, and 10.0.2.x before 10.0.2.4 allows remote authenticated users to hijack the authentication of arbitrary users for requests that insert XSS sequences.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site request forgery (CSRF) vulnerability in IBM Emptoris Contract Management, Sourcing Portfolio, and Spend Analysis allows an authenticated attacker to craft malicious requests that inject XSS sequences into other users' sessions by hijacking their authentication via forged requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 9.5.0.0= 9.5.0.1= 9.5.0.2= 9.5.0.3= 10.0.0.0= 10.0.0.1= 10.0.1.0= 10.0.1.1= 10.0.1.2= 10.0.2.0= 10.0.2.2= 9.5.0.0= 9.5.0.1= 9.5.0.2= 9.5.1.0= 9.5.1.1= 9.5.1.2= 10.0.0.0= 10.0.1.0= 10.0.1.1= 10.0.1.2= 10.0.2.0= 10.0.2.2= 9.5.0.0= 9.5.0.1= 9.5.0.2= 9.5.0.3= 9.5.0.4= 9.5.0.5= 9.5.0.6= 10.0.0.0= 10.0.0.1= 10.0.1.0= 10.0.1.1= 10.0.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed IBM Emptoris productCheck the application administrative console or system inventory for the product name (Emptoris Spend Analysis, Emptoris Sourcing Portfolio, or Emptoris Contract Management)Affected if The product is one of these three Emptoris applications
-
Determine the installed versionLocate the version information in the application's About section, help menu, or version file typically found in the installation directoryAffected if The installed version matches one of the versions listed in the affected products ranges (e.g., 9.5.0.0 through 10.0.2.2 for Spend Analysis)
-
Verify CSRF protection is absent or bypassedInspect the application's HTML forms for anti-CSRF tokens (hidden form fields or request headers) on state-changing operations such as user management, configuration changes, or data submissionsAffected if State-changing forms lack anti-CSRF tokens or the tokens can be omitted without rejection
If you have Emptoris Spend Analysis, Sourcing Portfolio, or Contract Management installed at an affected version (9.5.x or 10.0.x through 10.0.2.2, or 10.1.x through 10.1.1.2 for Contract Management) and the application lacks anti-CSRF tokens on sensitive operations, your environment is vulnerable to CVE-2014-3040.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens on all state-changing operations and configure SameSite cookie attributes to prevent cross-site request forgery attacks.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3040 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3040 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data