LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48330: WordPress Bulk Comment Remove Plugin <= 2 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Mike Strand Bulk Comment Remove allows Cross Site Request Forgery.This issue affects Bulk Comment Remove: from n/a through 2.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress plugin used to bulk-remove comments can be tricked into performing unwanted actions if an authenticated site administrator is lured into a malicious request. The business impact is mainly unauthorized comment removal or disruption, not data theft, based on the published CVSS vector.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is not evidenced as actively exploited, but affected sites could suffer unauthorized comment deletion if an administrator is targeted.

Technical view

CVE-2023-48330 is a CWE-352 CSRF issue in Mike Strand Bulk Comment Remove for WordPress, affecting versions through 2. The CVSS 3.1 score is 5.4, with network attack vector, low complexity, required user interaction, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites that have the Bulk Comment Remove plugin installed at version 2 or earlier. The source bundle does not identify other affected products or a confirmed fixed release.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not report active exploitation. Exploitation requires user interaction, likely involving an authenticated administrative context and a forged request.

Researcher notes

Evidence is sparse. Sources confirm CSRF, affected range through version 2, CVSS 5.4, and Patchstack as the vulnerability database reference. The bundle does not name a patch version, exploit activity, or detailed vulnerable endpoint.

Mitigation direction

  • Inventory WordPress sites for the Bulk Comment Remove plugin.
  • Confirm whether installed versions are 2 or earlier.
  • Check vendor or Patchstack guidance for a fixed release or mitigation.
  • Disable or remove the plugin if it is unused or unmaintained.
  • Limit administrator browsing exposure while remediation is pending.

Validation and detection

  • Review plugin inventory across production and staging WordPress sites.
  • Confirm plugin package name bulk-comment-remove and installed version.
  • Check administrative audit logs for unexpected bulk comment changes.
  • In staging, verify sensitive plugin actions require CSRF protection.
  • Document any site where patch status cannot be confirmed.
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-352: 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-48330 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:N/UI:R/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:N/UI:R/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-48330Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
Mike StrandBulk Comment Removebulk-comment-remove, n/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.