LiveActive security incident?Get immediate response
CVE Record

CVE-2023-39161: WordPress Discussion Board plugin <= 2.4.8 - Content Injection vulnerability

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in WP Discussion Board Discussion Board allows Content Spoofing, Cross-Site Scripting (XSS).This issue affects Discussion Board: from n/a through 2.4.8.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects WordPress sites using the Discussion Board plugin through version 2.4.8. A logged-in attacker may be able to inject misleading or script-related content, creating XSS/content-spoofing risk. The supplied sources do not show known active exploitation or a confirmed fixed version.

Executive priority

Treat this as a moderate website integrity risk. It is not currently evidenced as actively exploited in the supplied sources, but affected public WordPress sites should be inventoried and remediated during normal vulnerability cycles.

Technical view

CVE-2023-39161 is a CWE-80 basic XSS issue in WP Discussion Board Discussion Board through 2.4.8. CVSS 3.1 is 5.4 with network access, low attack complexity, low privileges required, and no user interaction. Reported impact is low integrity and availability loss, with no confidentiality impact.

Likely exposure

Exposure is limited to WordPress installations that have the wp-discussion-board plugin installed at version 2.4.8 or earlier. The CVSS vector indicates exploitation requires some authenticated or low-privilege access, not anonymous access.

Exploitation context

The source bundle marks CISA KEV as false and provides no evidence of active exploitation. PatchStack and CVE sources classify the issue as content injection/XSS, but the provided data does not include exploit maturity, public exploit details, or a named fix.

Researcher notes

Key gaps are fix status and exploitation evidence. Do not assume anonymous exploitation because CVSS lists PR:L. Validation should focus on plugin presence, version, reachable discussion functionality, and which authenticated roles can submit content.

Mitigation direction

  • Inventory WordPress sites for the Discussion Board plugin and installed versions.
  • Check WP Discussion Board or PatchStack guidance for a fixed release or mitigation.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict forum posting and content-management permissions to trusted users.
  • Review content security controls that reduce XSS impact where available.

Validation and detection

  • Confirm whether wp-discussion-board is installed on each WordPress site.
  • Flag any installed version at or below 2.4.8.
  • Review user roles that can submit or manage discussion content.
  • Check recent discussion content for unexpected HTML or script-like markup.
  • Monitor vendor advisories for a confirmed fixed version.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-80: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-39161 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-39161Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WP Discussion BoardDiscussion Boardwp-discussion-board, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-80 · source CWE mapping

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.