dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2023-51521

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 ExpressTech Quiz And Survey Master.This issue affects Quiz And Survey Master: from n/a through 8.1.18.

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 Quiz And Survey Master WordPress plugin allows attackers to induce authenticated users to perform unintended actions. The specific affected forms or AJAX endpoints within the plugin are not detailed in the available information.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations (forms and AJAX actions) within the plugin and upgrade to version 8.1.19 or later where the vulnerability is patched.

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

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
None
Integrity
Low
Availability
Low

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

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. Locate Quiz And Survey Master plugin
    In WordPress admin dashboard, go to Plugins > Installed Plugins and find 'Quiz And Survey Master' in the list
    Affected if Plugin is not installed or not found in the list
  2. Identify installed version
    In the plugins list, locate the version number displayed below the plugin name 'Quiz And Survey Master'
    Affected if Version is not displayed or cannot be determined from the plugins page
  3. Compare version to fixed release
    Compare your installed version number to 8.1.19 - any version below 8.1.19 (such as 8.1.18, 8.1.10, 7.x.x, etc.) falls within the affected range
    Affected if Installed version is lower than 8.1.19 (e.g., 8.1.18, 8.0.0, 7.3.2)
  4. Verify plugin is active
    Confirm the Quiz And Survey Master plugin status shows as 'Active' in the WordPress plugins list
    Affected if Plugin is active and version is below 8.1.19 - the vulnerable code is reachable

You are affected if Quiz And Survey Master plugin is installed, active, and running a version lower than 8.1.19.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all state-changing operations (forms and AJAX actions) within the plugin and upgrade to version 8.1.19 or later where the vulnerability is patched.

Have this fixed 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 help mitigating

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-51521 — 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-51521 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