CVE-2021-20451 is a medium severity (CVSS 6.0) SQL injection flaw in IBM Cognos Controller 10.4.1, 10.4.2 and 11.0.0. A remote attacker with high privileges could read or change back end data. IBM lists fix packs 10.4.1 FP1, 10.4.2 FP3 and 11.0.1 FP2, and no workaround.
What's affected
- IBM Cognos Controller 10.4.1, 10.4.2 and 11.0.0, per the NVD record and the IBM bulletin.
- IBM fixes: 10.4.1 FP1, 10.4.2 FP3, and 11.0.1 FP2 for the 11.0.0 line, all from Fix Central.
- IBM states that Controller on Cloud 11.x and 10.4.2.x environments have already been updated.
- IBM lists no workarounds or mitigations.
- The record shows privileges required as high, which is why the score is medium. KEV status: false.
How to check if you're exposed
Cognos Controller version details are in the product about information or the installed fix pack history on the Controller server. Compare what you find against the three releases above. If you run Controller on IBM cloud, IBM states the hosted environments are already updated.
If you are unsure which fix pack you are on, ask your IBM administrator or open a support case with IBM.
What to do now
- Identify which Controller release and fix pack each environment runs, including test and disaster recovery copies.
- Download the matching fix pack from IBM Fix Central: 10.4.1 FP1, 10.4.2 FP3, or 11.0.1 FP2.
- Apply it in a test environment first and run your close and consolidation checks.
- Review which accounts hold the high privileges the attack needs and trim them to what is necessary.
- Because IBM lists no workaround, plan the patch window rather than waiting.
Why it matters
The class is CWE-89, SQL injection. Input that should be treated as a value ends up interpreted as part of a database command, so an attacker can change what the query does. IBM describes the effect as the ability to view, add, modify or delete information in the back end database.
Financial consolidation systems hold sensitive numbers, and even a privileged only flaw deserves attention there. Those accounts can belong to people who are not database administrators, and the data integrity risk is the real concern for a finance team.
Quick check
Is there a workaround?
IBM lists none. Apply the fix pack for your release.
Does the 2021 date mean this is old news?
The CVE was published in the NVD in 2024, but the flaw is in versions IBM has already issued fix packs for. The issue for you is whether those fix packs are installed.
Sources
Last reviewed: 19 October 2026.