Discussion Board CVE-2025-8483
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain Subscriber account
-
DeliverySubmit crafted value to vulnerable plugin action
-
ExploitValue reaches do_shortcode without validation
-
ExecutionArbitrary shortcode executed in site context
-
ImpactInformation disclosure or content manipulation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated account with Subscriber-level access or above on a site running the Discussion Board - WordPress Forum Plugin at version 2.5.5 or earlier; the specific prerequisite is reaching the plugin action that passes an unvalidated user-supplied value into WordPress's do_shortcode() function. Limiting factors: exploitation is impossible without a valid low-privilege account, so sites that disallow open user registration materially reduce exposure, and the real-world impact is bounded by which shortcodes are actually registered on the target site (so escalation to code execution is conditional, not guaranteed). No user interaction from an admin is needed (UI:N). |
| Impact | This is a moderate-risk, authenticated vulnerability rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, base 6.3) indicates network-reachable, low-complexity exploitation requiring only Subscriber-level authentication (PR:L) with no user interaction, but each impact dimension is only Low - consistent with arbitrary shortcode execution whose blast radius depends on which shortcodes are available in the environment rather than guaranteed full compromise. Exploitation signals are weak: EPSS is 0.26% (17th percentile), there is no CISA KEV listing, and no public exploit code was identified in the provided data, so this is not evidence of widespread or imminent mass exploitation. The 'RCE' tag overstates the confirmed impact - the description and CWE-94 describe arbitrary shortcode execution, which only escalates to code execution if a dangerous shortcode happens to be registered on the site; treat 'RCE' as a worst-case label, not a confirmed outcome. Net: a real but lower-priority issue for sites running this plugin that allow untrusted user registration, warranting patching in normal cycles rather than crisis response. |
| Exploit ScenarioDerived | An attacker registers or already holds a low-privilege Subscriber account on a WordPress site running the Discussion Board plugin (≤2.5.5). They invoke the vulnerable plugin action with a crafted value that is passed to do_shortcode without proper validation, causing arbitrary shortcodes to be rendered and executed in the application context. No public exploit code was identified at time of analysis, and the low attack complexity (AC:L) means no special timing or conditions are needed once an account exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Authenticated shortcode injection in the Discussion Board - WordPress Forum Plugin (all versions through 2.5.5) lets any logged-in user with Subscriber-level access or higher trigger arbitrary WordPress shortcodes by supplying an unvalidated value to a plugin action that is then passed into do_shortcode(). The flaw requires a valid low-privilege account rather than being exploitable anonymously, and the practical severity depends on which shortcodes are registered on the target site, since only those can be invoked. CISA KEV does not list this CVE and no public exploit code has been identified at time of analysis, with EPSS at 0.26% (17th percentile).
RemediationAI
Primary fix: upgrade the Discussion Board - WordPress Forum Plugin past version 2.5.5 to the current release; upstream fix is available as a WordPress Trac changeset (3382300) for the wp-discussion-board component, and a released patched version tag is not independently confirmed from the provided data. If immediate upgrading is not possible, reduce exposure by disabling open user registration and removing or demoting Subscriber-level accounts so the authenticated prerequisite cannot be met - this closes the attack path but breaks community sign-up workflows. Additionally, audit which shortcodes are registered by other active plugins and themes and remove or restrict high-impact shortcodes (for example those that include files or render arbitrary templates); this lowers the consequence of a successful injection at the cost of losing that functionality. Consult the vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/a09659bc-e42b-4f08-a1a1-23e226be1be9?source=cve for ongoing guidance.
Affected ProductsAI
All versions of the Discussion Board - WordPress Forum Plugin up to and including 2.5.5 are vulnerable; no CPE identifier is supplied in the source data, so scoping should be done by plugin slug and installed version. Any WordPress installation with the plugin active at a vulnerable version and with accounts at Subscriber level or above is in scope for exploitation. Vendor and advisory references are the Wordfence threat intelligence page (https://www.wordfence.com/threat-intel/vulnerabilities/id/a09659bc-e42b-4f08-a1a1-23e226be1be9?source=cve) and the plugin's WordPress Trac changeset (https://plugins.trac.wordpress.org/changeset?old=3382300%40wp-discussion-board&new=3382300%40wp-discussion-board).
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-94 code injection: an action handler in the plugin fails to validate or sanitize a user-supplied parameter before passing it to WordPress core's do_shortcode() function, which evaluates any registered shortcode tag present in the string. Shortcodes are executable content, and many plugins register shortcodes that include files, render templates, or expose data, so control over the argument effectively grants the ability to run any shortcode registered on the target site - a conditional but real escalation path toward code execution and information disclosure. The assessed CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L) confirms remote, low-privilege exploitation with no user interaction and limited confidentiality, integrity, and availability impact. The WordPress plugin Trac changeset 3382300 for the wp-discussion-board component corresponds to the upstream fix for this issue.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Network-reachable action requires a valid Subscriber account (PR:L) with no interaction; shortcode execution yields limited, site-dependent confidentiality/integrity/availability impact, so C/I/A are Low.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The The Discussion Board - WordPress Forum Plugin plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.5.5. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB