CVE-2022-36120
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 · uneditedAn issue was discovered in Blue Prism Enterprise 6.0 through 7.01. In a misconfigured environment that exposes the Blue Prism Application server, it is possible for an authenticated user to reverse engineer the Blue Prism software and circumvent access controls for the getChartData administrative function. Using a low/no privilege Blue Prism user account, the attacker can alter the server's settings by abusing the getChartData method, allowing the Blue Prism server to execute any MSSQL stored procedure by name.
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 confidenceIn Blue Prism Enterprise 6.0-7.01, a misconfiguration exposing the application server allows authenticated users to bypass access controls on the getChartData administrative function. A low-privilege user can exploit this to alter server settings and execute arbitrary MSSQL stored procedures by name, achieving privilege escalation.
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>= 6.0, < 7.1CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 Blue Prism Enterprise versionLocate and check the installed Blue Prism version in the system (typically found in the application itself, installation directory, or registry)Affected if Installed version is >= 6.0 and < 7.1 (or if version cannot be determined but falls within or near this range)
-
Identify application server exposureDetermine whether the Blue Prism application server is listening on external/network-accessible interfaces versus localhost onlyAffected if The application server is accessible over the network (not bound to localhost/127.0.0.1)
-
Verify getChartData endpoint accessibilityCheck if the getChartData administrative function is exposed via the web interface or API endpointsAffected if The getChartData function is accessible without proper administrative authentication or authorization checks
-
Assess user role configurationReview the role-based access control (RBAC) configuration to determine if low-privilege users have access to administrative functionsAffected if Low-privilege or non-administrative users can access or invoke the getChartData administrative function
-
Confirm MSSQL backend usageVerify that Blue Prism is using Microsoft SQL Server as its database backendAffected if MSSQL is the database backend, as the vulnerability allows execution of arbitrary MSSQL stored procedures
If the installed Blue Prism Enterprise version is between 6.0 and 7.01 inclusive, the application server is network-exposed, and low-privilege users can access the getChartData administrative function, the environment is vulnerable to this CVE.
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.
dbcve · scoped7.1
Restrict network exposure of the Blue Prism Application server and implement proper role-based access controls on administrative functions like getChartData to prevent unauthorized stored procedure execution.
Blue Prism Enterprise 7.1 or later
- Verify current Blue Prism version by checking the About section in the Blue Prism product or via the installation directory version file
- Schedule a maintenance window for the upgrade process
- Review Blue Prism 7.1 release notes for any prerequisites or known issues before upgrading
- Create a full backup of the Blue Prism database and configuration files
- Test the upgrade in a non-production environment first
- Upgrade the Blue Prism Application server to version 7.1 or later
- Verify that the getChartData administrative function now properly enforces access controls
- Confirm that low-privilege users can no longer execute MSSQL stored procedures through this vector
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36120 — 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-2022-36120 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