CVE-2018-16952
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 · uneditedThe Oracle WebCenter Interaction Portal 10.3.3 does not implement protection against Cross-site Request Forgery in its design. The impact is sensitive actions in the portal (such as changing a portal user's password). NOTE: this CVE is assigned by MITRE and isn't validated by Oracle because Oracle WebCenter Interaction Portal is out of support.
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 · moderate confidenceOracle WebCenter Interaction Portal 10.3.3 lacks Cross-site Request Forgery (CSRF) protection in its design, allowing attackers to craft malicious requests that execute actions with the privileges of an authenticated user, such as changing portal user passwords.
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= 10.3.3CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Confirm Oracle WebCenter Interaction is installedLocate the WebCenter Interaction installation directory or check the Oracle Enterprise Manager for installed Oracle products. Look for the portal installation path, typically under the Oracle middleware home directory.Affected if Oracle WebCenter Interaction portal software is not found on the system
-
Verify the installed version is 10.3.3Check the version of Oracle WebCenter Interaction. This can typically be found in the portal's about page, the installation logs, or by querying the Oracle metadata. Common locations include the portal's system information page at /portal/server.pt or checking the installer README file.Affected if The installed version is anything other than exactly 10.3.3
-
Inspect forms for anti-CSRF token presenceLog into the WebCenter Interaction portal and navigate to state-changing forms such as the user profile password change form, user registration form, or admin configuration forms. View the page source (HTML) and examine all form elements for hidden input fields containing anti-CSRF tokens (commonly named like 'token', 'csrf', 'nonce', or similar).Affected if State-changing forms contain no anti-CSRF token fields or the tokens are not validated on submission
-
Test CSRF token validation on form submissionCapture a legitimate form submission using a proxy tool (such as Burp Suite or OWASP ZAP). Remove any token parameters from the request and resubmit it. Observe whether the server accepts or rejects the request.Affected if The server accepts the request without the token, indicating no server-side validation occurs
-
Check web server configuration for CSRF protectionExamine the WebCenter Interaction web server configuration (typically within the Oracle HTTP Server or embedded Pluck CMS configuration) for any custom anti-CSRF filters or middleware that may have been added as a compensating control.Affected if No anti-CSRF filter or protection mechanism is configured at the web server layer
The environment is affected if Oracle WebCenter Interaction version 10.3.3 is installed AND state-changing forms lack anti-CSRF token validation.
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 forms and validate them on the server side, or deploy a WAF with CSRF detection to block malicious requests.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16952 — 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-2018-16952 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