# CVE-2024-13692: Return Refund and Exchange For WooCommerce <= 4.4.5 - Authenticated (Subscriber+) Insecure Direct Object Reference

> Attackers can read and modify other users' order messages and refund attachments due to missing authorization checks in the plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2pq9-46mh-w84j

## What is CVE-2024-13692?

CVE-2024-13692 is a medium-severity missing authorization vulnerability in wpswings Return Refund and Exchange For WooCommerce, published on 14 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Return Refund and Exchange For WooCommerce – Return Management System, RMA Exchange, Wallet And Cancel Order Features plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.4.5 via several functions due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to overwrite linked refund image attachments, overwrite refund request message, overwrite order messages, and read order messages of other users.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2024-13692?

It affects 1 product.


Products: Wpswings Return Refund and Exchange for Woocommerce.

## How do I fix CVE-2024-13692?

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

## Is CVE-2024-13692 being exploited?

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

## Other vulnerabilities in wpswings Return Refund and Exchange For WooCommerce

- [CVE-2022-4047](https://insights.sbomify.com/CVE-2022-4047/): Return Refund and Exchange For WooCommerce < 4.0.9 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2024-13641](https://insights.sbomify.com/CVE-2024-13641/): Information disclosure in Return Refund and Exchange For WooCommerce (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13692 and fix it if it is affected.

What it is: CVE-2024-13692 is a medium-severity missing authorization vulnerability in wpswings Return Refund and Exchange For WooCommerce, published on 14 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13692 in the wild and no public exploit code.

Affected product: wpswings Return Refund and Exchange For WooCommerce. 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-2024-13692/ (Markdown: https://insights.sbomify.com/CVE-2024-13692/index.md)
```

## Sources

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

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