LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25449: WordPress CformsII Plugin <=15.0.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Oliver Seidel, Bastian Germann cformsII plugin <= 15.0.4 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-25449 is a CSRF issue in the WordPress cformsII plugin through version 15.0.4. If a logged-in site user can be tricked into visiting a malicious page, an attacker may cause an unintended low-impact change. The provided sources do not show active exploitation or a confirmed fixed version.

Executive priority

Treat this as a targeted WordPress hygiene issue, not an emergency. Remediate where the plugin is present, especially on business-critical public sites, because CSRF can undermine administrative intent even with modest CVSS impact.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in cformsII/cforms2. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, and no confidentiality or availability impact. Evidence does not describe the affected action or a patch.

Likely exposure

Exposure is limited to WordPress sites running the cformsII plugin at version 15.0.4 or earlier. Sites not using cformsII are not exposed based on the supplied sources.

Exploitation context

The CVE is not listed as CISA KEV, and the provided sources do not state active exploitation. Exploitation would require user interaction, likely involving a logged-in WordPress user being induced to trigger an unwanted request.

Researcher notes

The source bundle confirms the vulnerability class, affected plugin, version boundary, CVSS vector, and CWE. It does not provide vulnerable endpoints, affected actions, proof-of-concept details, exploitation evidence, or a fixed version, so validation should remain version- and vendor-guidance focused.

Mitigation direction

  • Inventory WordPress sites for cformsII/cforms2 version 15.0.4 or earlier.
  • Check vendor or Patchstack guidance for a fixed release or official mitigation.
  • Disable or replace the plugin if no supported fix is available.
  • Prioritize remediation on public sites with active WordPress administrators.

Validation and detection

  • Confirm whether each WordPress site has cformsII/cforms2 installed.
  • Record installed plugin versions and compare against 15.0.4 or earlier.
  • Review WordPress admin activity for unexpected cformsII configuration changes.
  • Check whether vendor guidance identifies a patched version before upgrade planning.
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-25449 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-25449Attack 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
Oliver Seidel, Bastian GermanncformsIIcforms2, 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.