dbcve.org
LeykaWordPress extension · Techsoupeurope

CVE-2023-27442

HIGH · 8.8 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 3.29.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Teplitsa of social technologies Leyka plugin <= 3.29.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Leyka WordPress donation plugin versions 3.29.2 and below allows attackers to perform unauthorized state-changing actions on behalf of authenticated administrators or users by tricking them into visiting malicious websites.

MitigationUpgrade Leyka plugin to version 3.29.3 or later; implement anti-CSRF nonce verification on all state-changing form submissions and AJAX endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LeykaWordPress extension
Affected:<= 3.29.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Leyka plugin installation
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Leyka' in the list of installed plugins, or check the file system at wp-content/plugins/ for a leyka directory.
    Affected if Leyka plugin is not found in the WordPress installation
  2. Determine installed Leyka version
    In WordPress admin, go to Plugins > Installed Plugins and find the Leyka plugin entry. The version number is displayed below the plugin name. Alternatively, check the main plugin file header in wp-content/plugins/leyka/class-leyka-plugin.php for the 'Version' header.
    Affected if Version cannot be determined or plugin files are missing
  3. Compare version against affected range
    Compare the installed version number to the affected range: 3.29.2 and below. If the version is 3.29.2 or lower (e.g., 3.29.1, 3.29.0, 3.28.0, etc.), the plugin is in the vulnerable version range.
    Affected if Installed version is 3.29.2 or any version lower than 3.29.2 (e.g., 3.29.1, 3.28.5)
  4. Identify state-changing endpoints lacking CSRF protection
    Examine the Leyka plugin source code in wp-content/plugins/leyka/ for form submissions and AJAX handlers. Look for wp_verify_nonce or wp_create_nonce calls in files handling donations, settings changes, or user actions. Check common state-changing files: leyka-ajax.php, leyka-donation.php, or files in the /includes/ directory.
    Affected if State-changing form handlers or AJAX endpoints are found without nonce verification tokens

The environment is affected if Leyka plugin version 3.29.2 or below is installed, as this version range lacks proper CSRF nonce validation on state-changing actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.29.2
Interim mitigation

Upgrade Leyka plugin to version 3.29.3 or later; implement anti-CSRF nonce verification on all state-changing form submissions and AJAX endpoints.

Recommended fix Moderate confidence

Upgrade to Leyka version 3.30 or later (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Leyka plugin in the list
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload it
  5. Verify the update completed successfully by checking the plugin version is greater than 3.29.2
  6. Test critical donation/fundraising workflows to confirm functionality remains intact
Caveat Review plugin changelog for any breaking changes between 3.29.2 and the target version; test in staging if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Leyka Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27442 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-27442 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data