# CVE-2025-1513: Cross-site scripting in Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe

> Unauthenticated attackers can inject arbitrary scripts via comment fields in this WordPress gallery plugin, affecting all users viewing the pages.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-4h65-5qp6-cgrp

## What is CVE-2025-1513?

CVE-2025-1513 is a high-severity cross-site scripting vulnerability in contest-gallery Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Photos, Files, YouTube, Twitter, Instagram, TikTok, Ecommerce Contest Gallery – Upload, Vote, Sell via PayPal or Stripe, Social Share Buttons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Name and Comment field when commenting on photo gallery entries in all versions up to, and including, 26.0.0.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

## Which versions are affected by CVE-2025-1513?

It affects 1 product.


Products: Contest-Gallery Contest Gallery.

## How do I fix CVE-2025-1513?

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

## Is CVE-2025-1513 being exploited?

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

## Other vulnerabilities in contest-gallery Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe

- [CVE-2024-11103](https://insights.sbomify.com/CVE-2024-11103/): Contest Gallery <= 24.0.7 - Unauthenticated Arbitrary Password Reset to Privilege Escalation/Account Takeover (critical 9.8)
- [CVE-2024-10687](https://insights.sbomify.com/CVE-2024-10687/): SQL injection in Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe (critical 9.8)
- [CVE-2019-5974](https://insights.sbomify.com/CVE-2019-5974/): Cross-site request forgery in Contest Gallery (high 8.8)
- [CVE-2024-32778](https://insights.sbomify.com/CVE-2024-32778/): WordPress Contest Gallery plugin <= 21.3.4 - Arbitrary File Deletion vulnerability (high 8.5)
- [CVE-2024-30236](https://insights.sbomify.com/CVE-2024-30236/): WordPress Contest Gallery plugin <= 21.3.4 - SQL Injection vulnerability (high 8.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1513 and fix it if it is affected.

What it is: CVE-2025-1513 is a high-severity cross-site scripting vulnerability in contest-gallery Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1513 in the wild and no public exploit code.

Affected product: contest-gallery Contest Gallery – Upload & Vote Photos, Media, Sell with PayPal & Stripe. 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-2025-1513/ (Markdown: https://insights.sbomify.com/CVE-2025-1513/index.md)
```

## Sources

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

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