---
title: "Why does uploading an image to Content Store fail with XSS error due to suspicious content?"
slug: "uploading-image-to-content-store-fails-with-xss-error-due-to-suspicious-content"
status: "update"
updated: 2026-10-21T10:42:59Z
published: 2026-10-21T10:42:59Z
canonical: "docs.mapp.com/uploading-image-to-content-store-fails-with-xss-error-due-to-suspicious-content"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why does uploading an image to Content Store fail with XSS error due to suspicious content?

Uploading an image to the Content Store can fail with the message “Cannot execute action because XSS scanner found suspicious content!” This is unexpected, because an image should not contain cross-site scripting elements.

---

## Cause

This can happen when an image was saved with an Adobe product such as Photoshop or Lightroom. The application adds metadata to the image. Metadata is user- or application-defined information about the image that is not part of the displayed image itself.

If this metadata contains URLs or unexpected binary data, the upload fails after the check for suspicious content.

---

## Solution

Save the image without metadata, or make sure that the metadata does not contain URLs or JavaScript. You can:

- Use the export or “save for web” option of your tool and select the option to remove metadata.
- Change the settings of your tool so that it does not add metadata to images.
- Open the image in another image editor, such as Paint.NET on Windows or Krita on Mac, and save it with a new name. This removes most or all metadata and keeps only the image data.
- Clean the file with an external tool such as [ExifTool](https://exiftool.org/).

Once the metadata is removed, the file is often smaller. Mapp Engage no longer detects suspicious content, and you can upload the file to the Content Store.

*Document Technical Reference: h9qvb*