# CVE-2026-97317: Giveaways and Contests by RafflePress < 1.12.27 - Unauthenticated reCAPTCHA Secret Key Disclosure via Giveaway Page

> Unauthenticated attackers can retrieve reCAPTCHA secret keys from public giveaway pages in the RafflePress WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-82gv-pr29-8vm2

## What is CVE-2026-97317?

CVE-2026-97317 is a medium-severity vulnerability in Unknown Giveaways and Contests by RafflePress, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Giveaways and Contests by RafflePress  WordPress plugin before 1.12.27 does not remove the reCAPTCHA secret key from the giveaway settings it embeds in public giveaway pages, allowing unauthenticated visitors to retrieve the secret key of any active giveaway that has reCAPTCHA configured.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-97317?


## How do I fix CVE-2026-97317?

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

## Is CVE-2026-97317 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97317 and fix it if it is affected.

What it is: CVE-2026-97317 is a medium-severity vulnerability in Unknown Giveaways and Contests by RafflePress, published on 2 Oct 2026. 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-2026-97317 in the wild and no public exploit code.

Affected product: Unknown Giveaways and Contests by RafflePress. 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-2026-97317/ (Markdown: https://insights.sbomify.com/CVE-2026-97317/index.md)
```

## Sources

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

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