LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36691: WordPress WebwinkelKeur Plugin <= 3.24 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Albert Peschar WebwinkelKeur plugin <= 3.24 versions.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-36691 affects the WordPress WebwinkelKeur plugin, reported for versions up to 3.24. A successful CSRF attack could cause a logged-in site user to unintentionally make a limited change. The available sources rate it medium severity and do not show active exploitation.

Executive priority

Treat as a moderate WordPress hygiene item, not an emergency based on current evidence. Prioritize internet-facing business sites using this plugin, especially where WordPress administrators frequently access external links while logged in.

Technical view

The issue is CWE-352 Cross-Site Request Forgery in Albert Peschar WebwinkelKeur for WordPress. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact. The bundle does not identify a specific vulnerable action or fixed version.

Likely exposure

Exposure is likely limited to WordPress sites with the WebwinkelKeur plugin installed at version 3.24 or earlier. Sites without the plugin, or outside the stated version range, are not shown as affected by the supplied sources.

Exploitation context

The source bundle does not cite KEV listing or active exploitation. CSRF generally requires a victim user interaction while authenticated to the affected WordPress site. The CVSS vector indicates no attacker privileges are required, but user interaction is required.

Researcher notes

Evidence is thin. The supplied data names CSRF and the <=3.24 range, but does not describe the vulnerable endpoint, required victim role, nonce failure, exploit maturity, or fixed version. Avoid asserting exploitability details beyond the CVSS vector and advisory title.

Mitigation direction

  • Inventory WordPress sites for the WebwinkelKeur plugin.
  • Check whether installed versions are 3.24 or earlier.
  • Review vendor, WordPress.org, or Patchstack guidance for a fixed release.
  • Update according to official vendor guidance when available.
  • Restrict administrative sessions and use normal CSRF-aware operational controls.

Validation and detection

  • Confirm whether WebwinkelKeur is installed on each WordPress site.
  • Record the installed plugin version and compare it with the <=3.24 range.
  • Review site logs for unusual plugin-setting changes around authenticated sessions.
  • Verify remediation only against vendor or trusted advisory guidance.
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-36691 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-36691Attack 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
Albert PescharWebwinkelKeurwebwinkelkeur, 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.