LiveActive security incident?Get immediate response
CVE Record

CVE-2023-37392: WordPress WP Dummy Content Generator Plugin <= 2.3.0 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Deepak Anand WP Dummy Content Generator plugin <= 2.3.0 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-37392 is a CSRF issue in the WordPress WP Dummy Content Generator plugin through version 2.3.0. It may let an attacker cause limited unauthorized changes if a user can be tricked into interacting while authenticated. The public bundle does not name a fixed version.

Executive priority

Treat as a routine but real WordPress hygiene issue. It is not supported as actively exploited by the provided sources, but affected production sites should be inventoried and remediated because CSRF can enable unauthorized changes through trusted users.

Technical view

The record describes CWE-352 in Deepak Anand's WP Dummy Content Generator plugin <=2.3.0, package wp-dummy-content-generator. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites running WP Dummy Content Generator version 2.3.0 or earlier. The bundle does not identify vulnerable endpoints, required victim role, or exact affected actions, so asset owners should verify plugin presence and version before assigning urgency.

Exploitation context

No provided source states active exploitation, and the CVE is not listed as KEV. The CVSS vector indicates exploitation requires user interaction. CSRF generally depends on a victim's authenticated browser session, but the source bundle does not provide exploit mechanics.

Researcher notes

Evidence is sparse. The bundle identifies CSRF, affected plugin, version boundary, CVSS, CWE, and Patchstack reference, but not the endpoint, nonce failure detail, vulnerable action, fixed version, or proof of exploitation. Avoid assuming impact beyond low integrity and availability.

Mitigation direction

  • Inventory WordPress sites for WP Dummy Content Generator installations.
  • Check whether installed versions are 2.3.0 or earlier.
  • Review vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Disable or remove the plugin where it is not required.
  • Prioritize remediation for admin-facing or production WordPress sites.

Validation and detection

  • Confirm plugin name and version from WordPress administration or asset inventory.
  • Check Patchstack and CVE records for updated remediation details.
  • Verify the plugin is removed, disabled, or updated according to vendor guidance.
  • Review change logs for unexpected content-generation or plugin-setting changes.
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-37392 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-37392Attack 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
Deepak AnandWP Dummy Content Generatorwp-dummy-content-generator, 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.