LiveActive security incident?Get immediate response
CVE Record

CVE-2023-48754: WordPress Delete Post Revisions In WordPress Plugin <= 4.6 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Wap Nepal Delete Post Revisions In WordPress allows Cross Site Request Forgery.This issue affects Delete Post Revisions In WordPress: from n/a through 4.6.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-48754 is a CSRF issue in the WordPress plugin Delete Post Revisions In WordPress through version 4.6. An attacker may be able to trick a user’s browser into making unwanted plugin-related requests. The cited CVSS impact is limited to low integrity and availability impact, with no confidentiality impact.

Executive priority

Treat this as a moderate WordPress hygiene issue. It is not evidenced as actively exploited, but exposed WordPress plugins are common entry points. Prioritize discovery and remediation on public business sites, especially where content integrity or operational uptime matters.

Technical view

The vulnerability is CWE-352 in Wap Nepal Delete Post Revisions In WordPress, package delete-post-revisions-on-single-click, affecting versions through 4.6. CVSS 3.1 is 5.4: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality impact, low integrity and availability impact.

Likely exposure

Exposure is likely limited to WordPress sites that have Delete Post Revisions In WordPress installed at version 4.6 or earlier. The source bundle does not identify affected CPEs, exact vulnerable endpoints, or whether later safe versions exist.

Exploitation context

The CVE is not listed as KEV in the source bundle, and no cited source reports active exploitation. The attack class requires user interaction. The bundle does not provide exploit details, vulnerable request paths, or precise role requirements.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. Do not assume exploitability beyond CSRF characteristics and the CVSS vector. Further analysis should confirm the vulnerable action, required victim role, nonce or capability checks, and whether a patched release exists.

Mitigation direction

  • Inventory WordPress sites for the delete-post-revisions-on-single-click plugin.
  • Check Patchstack and vendor guidance for a fixed version or official remediation.
  • Disable or remove the plugin where it is not operationally required.
  • Restrict WordPress administrative access to trusted users and hardened sessions.
  • Monitor plugin activity and site change logs for unexpected revision-deletion behavior.

Validation and detection

  • Confirm whether the plugin is installed and record its version.
  • Flag any installation running version 4.6 or earlier.
  • Review WordPress logs for unexpected plugin-related state changes.
  • Verify remediation against vendor or Patchstack guidance before closing the finding.
  • Document any compensating controls if no fixed version is available.
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-48754 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-48754Attack 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
Wap NepalDelete Post Revisions In WordPressdelete-post-revisions-on-single-click, 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.