Safeguard
Vulnerability Analysis•

CVE-2022-47072: Critical SQL Injection in Sparx Enterprise Architect

CVE-2022-47072 is a critical (9.8) SQL injection in Sparx Enterprise Architect 16.0.1605 32 bit. Check the vendor's release notes and update the tool.

Safeguard Security Team
3 min read

CVE-2022-47072 is a critical (CVSS 9.8) SQL injection flaw in Sparx Systems Enterprise Architect 16.0.1605, 32 bit. The Find field in the Select Classifier dialog is passed into SQL commands. I could not confirm a fixed version, so check the vendor's release notes and update.

What's affected

The record lists Enterprise Architect 16.0.1605 for 32 bit systems. Whether later 16.0 builds or the 64 bit edition are affected is not stated in the record. The only reference is a public repository by Dojo Security, which I could not load.

The NVD record was published on 31 January 2024. The vector is rated network, low complexity, no privileges, which is how NVD scored it. Enterprise Architect is a desktop modeling tool, so judge exposure by how your team connects it to shared model repositories.

How to check if you're exposed

In Enterprise Architect, open Help, About and read the build number. Check whether your teams run 32 bit or 64 bit installs, and whether models live in shared database repositories.

Then compare the build with the vendor's release history for a build that names a fix for the Select Classifier search.

What to do now

  1. Find every Enterprise Architect install and its build number.
  2. Update to the newest build from the vendor, and read its release notes for security fixes.
  3. Use database accounts for model repositories with only the rights users need, so a bad query cannot reach other data.
  4. Back up shared model repositories before and after the update.
  5. Treat model files from outside your team with the same care as any untrusted document.

Why it matters

CWE-89 is SQL injection. A value typed by the user is placed into a SQL statement without being separated from the query itself, so the text can change what the query does. The standard fix is parameterized queries.

The record scores confidentiality, integrity and availability as high. The reach of the flaw depends on what database sits behind the tool. KEV is false and the record contains no evidence of exploitation. I am deliberately not describing how the input is shaped, since the defensive steps are the same: update and limit database rights.

Quick check

Is a fixed version confirmed?

Not from the sources I could read. Check Sparx Systems release notes.

How do I reduce the damage while waiting?

Give the tool's database account the minimum rights it needs, and back up repositories.

Sources

You can also run the free in-browser dependency scan at gold.safeguard.sh/scan to see which known vulnerabilities your dependencies carry.

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.