LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24403: WordPress bbPress Voting Plugin <= 2.1.11.0 is vulnerable to Cross-Site Scripting (XSS)

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in WP For The Win bbPress Voting plugin <= 2.1.11.0 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-24403 is a stored cross-site scripting issue in the WordPress bbPress Voting plugin up to 2.1.11.0. It requires admin-level access, which lowers likelihood, but stored script execution can create persistent site-side risk if an administrator account is misused or compromised.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is not evidenced as actively exploited, but admin-level stored XSS can become material if administrator credentials are compromised or plugin governance is weak.

Technical view

The source describes authenticated admin-plus stored XSS in WP For The Win bbPress Voting, package bbp-voting. It is CWE-79 with CVSS 3.1 score 5.9: network reachable, low complexity, high privileges required, no user interaction, unchanged scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites with WP For The Win bbPress Voting installed at version 2.1.11.0 or earlier. The bundle does not provide CPEs or deployment prevalence, so asset inventory is needed to confirm reachability.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The high-privilege requirement means the most relevant scenarios involve malicious administrators, compromised admin accounts, or weak operational controls around WordPress administration.

Researcher notes

Evidence is narrow: public sources identify the plugin, affected range, CWE, and CVSS vector, but do not provide exploit detail, a named patched version, or observed exploitation. Validation should focus on confirmed plugin presence and vendor remediation status.

Mitigation direction

  • Inventory WordPress sites for the bbPress Voting plugin and installed version.
  • Check vendor or Patchstack guidance for an official fixed or recommended version.
  • Disable or remove the plugin where it is unnecessary or no safe version is available.
  • Restrict WordPress administrator access to trusted users with MFA.
  • Review administrator account activity for unexpected content or configuration changes.

Validation and detection

  • Confirm whether package bbp-voting is installed on any WordPress instance.
  • Record plugin versions and flag any at 2.1.11.0 or earlier.
  • Verify WordPress admin users are expected, active, and protected by MFA.
  • Check web content and plugin settings for unexpected stored script-like changes.
  • Document whether vendor guidance identifies a patched version or workaround.
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-79: 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-24403 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.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L1.23.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/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 For The WinbbPress Votingbbp-voting, n/aunaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.