LiveActive security incident?Get immediate response
CVE Record

CVE-2023-41864: WordPress PeproDev CF7 Database plugin <= 1.8.0 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Pepro Dev. Group PeproDev CF7 Database.This issue affects PeproDev CF7 Database: from n/a through 1.8.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-41864 is a CSRF issue in the WordPress PeproDev CF7 Database plugin through version 1.8.0. An attacker would need to trick a user into interacting with malicious content, potentially causing a low-impact unauthorized change. The provided sources do not identify active exploitation or a confirmed fixed version.

Executive priority

Treat this as a routine but real WordPress hygiene item. It is not currently evidenced as exploited and has medium severity, but affected public websites should be inventoried and remediated promptly because CSRF can enable unauthorized integrity-impacting actions.

Technical view

The issue is classified as CWE-352, Cross-Site Request Forgery. CVSS 3.1 is 4.3, with network reachability, low attack complexity, no attacker privileges, required user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. The exact vulnerable action is not described in the supplied sources.

Likely exposure

Exposure is limited to WordPress sites running PeproDev CF7 Database version 1.8.0 or earlier. Practical risk depends on whether an attacker can induce a logged-in site user to interact with attacker-controlled content. Sites not using this plugin are not indicated as affected.

Exploitation context

The CVE is not listed in CISA KEV, and the supplied sources do not claim active exploitation. CSRF generally requires social engineering of a user with an active authenticated session. No exploit details are provided in the source bundle.

Researcher notes

Evidence is sparse. The sources identify product, version range, CWE, and CVSS, but do not describe the vulnerable endpoint, required victim role, affected action, proof of concept, or fixed version. Avoid assuming broader Contact Form 7 or WordPress core exposure.

Mitigation direction

  • Inventory WordPress sites for the pepro-cf7-database plugin.
  • Identify any installations at version 1.8.0 or earlier.
  • Check vendor, WordPress, or Patchstack guidance for a fixed release.
  • Disable or remove the plugin if it is not business-required.
  • Limit privileged WordPress access until remediation is confirmed.

Validation and detection

  • Confirm installed plugin name, slug, and version on each WordPress site.
  • Compare findings against CVE and Patchstack affected-version metadata.
  • Review administrative activity for unexpected plugin-related changes.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
  • Track source updates because the supplied bundle lacks fixed-version details.
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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-41864 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
4.3 (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:N

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2023-41864Attack 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:N

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
Pepro Dev. GroupPeproDev CF7 Databasepepro-cf7-database, 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.