dbcve.org
Magayo Lottery ResultsWordPress extension · Magayo

CVE-2024-13522

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 2.0.12 or later.
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
The magayo Lottery Results plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.12. This is due to missing or incorrect nonce validation on the 'magayo-lottery-results' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

The magayo Lottery Results WordPress plugin lacks proper nonce validation on its settings page, allowing unauthenticated attackers to forge administrative requests. This CSRF vulnerability enables attackers to modify plugin settings and inject malicious scripts by tricking administrators into clicking crafted links.

MitigationUpdate to version 2.0.13 or later when available; implement WordPress nonces (wp_nonce_field) on all form submissions and admin actions to prevent CSRF attacks.

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
Magayo Lottery ResultsWordPress extension
Affected:<= 2.0.12

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

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

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. Confirm magayo Lottery Results plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'magayo Lottery Results' or 'Magayo Magayo Lottery Results'. Note the installed version displayed.
    Affected if The plugin is installed and the version is 2.0.12 or lower
  2. Verify plugin is active
    Check the Plugins page in WordPress admin to confirm the magayo Lottery Results plugin shows as 'Active'.
    Affected if The plugin is active and at version 2.0.12 or lower - only active plugins with this vulnerability can be exploited
  3. Inspect settings handler for nonce validation
    Access the plugin files via wp-content/plugins/ directory. Locate the file handling settings submissions (often named settings.php, admin.php, or similar). Search for 'nonce' or 'wp_verify_nonce' within that file.
    Affected if The settings handler file does not contain wp_verify_nonce, check_admin_referer, or wp_nonce_field calls when processing settings changes
  4. Check for CSRF protection on admin actions
    Examine the plugin PHP files for admin action handlers. Look for functions that process GET or POST requests from the settings page without validating a nonce token.
    Affected if Admin actions modify settings without requiring a valid nonce token verification

If the magayo Lottery Results plugin is active at version 2.0.12 or below and its settings handlers lack nonce validation, the environment is vulnerable to CVE-2024-13522.

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 2.0.12
Interim mitigation

Update to version 2.0.13 or later when available; implement WordPress nonces (wp_nonce_field) on all form submissions and admin actions to prevent CSRF attacks.

Recommended fix Moderate confidence

Latest version beyond 2.0.12 (check wordpress.org for current release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Magayo Lottery Results' in the plugin list
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin settings remain configured correctly

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

Fix this in Magayo Lottery Results 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-2024-13522 — 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-2024-13522 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