Safeguard
Vulnerability Analysis•

CVE-2023-27168: Critical File Upload RCE in Xpand IT Write-Back

CVE-2023-27168 is a critical file upload flaw in Xpand IT Write-Back Manager 2.3.1 that allows code execution. Update Write-Back to 4.1 or later.

Safeguard Security Team
4 min read

CVE-2023-27168 is a critical (CVSS 9.8) unrestricted file upload in Xpand IT Write-Back Manager 2.3.1, a Tableau extension, that can lead to code execution on the server. The researchers who found it say customers should update Write-Back to at least version 4.1.

What's affected

The record names Write-Back Manager 2.3.1 and says attackers can execute arbitrary code via a crafted jsp file. The researcher advisory from Balwurk gives the same affected version, 2.3.1, and states the mitigation: all affected customers should update Write-Back to at least version 4.1. Its timeline says an official patch was released by the Write-Back team on 12 July 2023.

The severity matches. The researchers score it 9.8 with a network vector, low complexity, no privileges and no user interaction, and the record shows the same figures. I did not find a separate vendor advisory in the references, which are the researchers' two write ups and the vendor home pages. Confirm the fixed release with Xpand IT.

The weakness is CWE-434, unrestricted upload of a file with a dangerous type. The write up says it can be chained with a separate weak signing secret issue, CVE-2023-27172, so an unauthenticated attacker can take over a vulnerable Write-Back Manager. I do not repeat the technical steps.

How to check if you're exposed

Write-Back is a Tableau extension with its own server and a Manager web interface. Open the Manager interface and read the version shown for your installation, or check your deployment records. Anything reported as 2.3.1 is named in the record, and the researchers advise at least 4.1.

Also check whether the Manager interface is reachable from networks that do not need it. The researchers describe the Manager as deployed on the same machine as the Write-Back installation, so find those machines on your server inventory. Look in the web root for files with unexpected extensions, such as jsp files you did not deploy.

To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.

What to do now

  1. Locate every Write-Back and Write-Back Manager installation.
  2. Update to version 4.1 or later, as the researchers advise.
  3. Restrict access to the Manager interface to administrators and trusted networks.
  4. Check the web root and logs for jsp files or upload requests you do not recognize.
  5. Rotate secrets used by the application after patching, including the signing secret, as a precaution.

Why it matters

Unrestricted file upload turns a feature meant for data into a way to place code on the server. If the server then runs the uploaded file, whoever can reach the upload handler can run code with the server's rights. The researchers report code execution as SYSTEM on the host.

What lifts this to critical is the lack of login. The record and write up both show no privileges required. The record does not flag the CVE in CISA KEV, and the write up describes a coordinated disclosure from a penetration test, not attacks in the wild.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Which version should I run?

The researchers advise at least version 4.1. Confirm with Xpand IT.

Is a login needed?

No. The record shows no privileges required, and the write up describes an unauthenticated attacker.

Sources

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.