CVE-2021-2406
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 · uneditedVulnerability in the Oracle Collaborative Planning product of Oracle E-Business Suite (component: User Interface). Supported versions that are affected are 12.1.1-12.1.3. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Collaborative Planning. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Collaborative Planning accessible data as well as unauthorized access to critical data or complete access to all Oracle Collaborative Planning accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
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 confidenceSQL injection or similar input validation flaw in Oracle Collaborative Planning UI allows low-privileged authenticated users to craft malicious HTTP requests that bypass normal access controls, enabling unauthorized data modification (insert/update/delete) and confidential data exfiltration.
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>= 12.1.1, <= 12.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 Collaborative Planning is installedLocate the Oracle E-Business Suite installation and identify if the Collaborative Planning module is present. This is typically found in the Oracle Applications manager or through the AD_BUGS or FND_PRODUCT_INSTALLATIONS tables in the Oracle database.Affected if The Collaborative Planning module is present in the Oracle E-Business Suite environment.
-
Check the installed versionQuery the version of Oracle Collaborative Planning using Oracle Applications manager, the FND_PRODUCT_INSTALLATIONS table, or the Oracle Applications patch level reports. Compare against the affected range: 12.1.1 through 12.1.3.Affected if The installed version is 12.1.1, 12.1.2, or 12.1.3.
-
Verify the Collaborative Planning UI is accessibleCheck if the Collaborative Planning web interface is enabled and accessible. This is typically served through the Oracle Applications Web Tier (Oracle HTTP Server). Look for the /oa_html/ or /OA_HTML/ directory paths that host the Collaborative Planning UI.Affected if The Collaborative Planning UI is accessible via web URLs such as /oa_html/ or similar Oracle Application Framework paths.
-
Confirm authentication mechanisms are in placeReview the Oracle E-Business Suite authentication configuration and verify that low-privileged users can access the Collaborative Planning UI. Check for proper Oracle Application Framework (OAF) security configurations and session management.Affected if Low-privileged authenticated users can access the Collaborative Planning UI without additional security restrictions.
Your environment is affected if Oracle Collaborative Planning version 12.1.1 through 12.1.3 is installed and the UI component is accessible to authenticated users.
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 dataApply Oracle Critical Patch Update (CPU) patches for Oracle E-Business Suite 12.1.1-12.1.3; verify patch compatibility in test environment before production deployment.
- Consultation4.0 h
- Implementation6.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2406 — 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-2021-2406 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