# CVE-2013-1783: Cross-site scripting in n/a

> Authenticated users with theme administration rights can inject arbitrary scripts into the Drupal Business theme's slide gallery.

- **Severity:** Low 2.1 (`AV:N/AC:H/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Mar 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3v57-5947-5vgp

## What is CVE-2013-1783?

CVE-2013-1783 is a low-severity cross-site scripting vulnerability in n/a, published on 27 Mar 2013. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the 3 slide gallery in page--front.tpl.php in the Business theme before 7.x-1.8 for Drupal allows remote authenticated users with the administer themes permission to inject arbitrary web script or HTML via unspecified vectors.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2013-1783?

It affects 1 product.


Products: Devsaran Business.

## How do I fix CVE-2013-1783?

No fix has been published for CVE-2013-1783 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-1783 being exploited?

There is no known exploitation of CVE-2013-1783 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1783 and fix it if it is affected.

What it is: CVE-2013-1783 is a low-severity cross-site scripting vulnerability in n/a, published on 27 Mar 2013. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-1783 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-1783/ (Markdown: https://insights.sbomify.com/CVE-2013-1783/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-1783
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-1783
- OSV: https://osv.dev/vulnerability/CVE-2013-1783

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-1783/
Summaries are generated and may contain mistakes; the official description above is the record.