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

CVE-2024-9592

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 Easy PayPal Gift Certificate plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.2.3. This is due to missing or incorrect nonce validation on the 'wpppgc_plugin_options' function. This makes it possible for unauthenticated attackers to update the plugin's settings and inject malicious JavaScript 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 · high confidence

The Easy PayPal Gift Certificate WordPress plugin (versions up to 1.2.3) lacks proper nonce validation in its wpppgc_plugin_options function, enabling unauthenticated attackers to forge administrative requests. By tricking a site administrator into clicking a malicious link, attackers can update plugin settings and inject arbitrary JavaScript into the WordPress site.

MitigationApply vendor-supplied patch or update to the latest plugin version which includes proper nonce validation. Until a patch is available, review plugin settings pages for any unauthorized changes and monitor for malicious script injections.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Verify if the Easy PayPal Gift Certificate plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'easy-paypal-gift-certificate' or similar. If the plugin was removed, check for any residual files.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named easy-paypal-gift-certificate.php or similar in the plugin folder) and locate the 'Version' header in the plugin comment block at the top of the file.
    Affected if The reported version is 1.2.3 or lower
  3. Confirm the vulnerable function exists in the code
    Search the plugin PHP files for the function 'wpppgc_plugin_options' - examine the function definition to see if it includes nonce verification (look for 'check_admin_referer', 'wp_verify_nonce', or 'nonce_field' calls near the beginning of the function.
    Affected if The wpppgc_plugin_options function exists but does not contain nonce validation logic at the start of the function
  4. Review plugin settings for unauthorized modifications
    Access the WordPress admin panel, navigate to the plugin settings page (usually under Settings or a dedicated menu item for this plugin), and inspect all saved option values for any unexpected or malicious content.
    Affected if Plugin settings contain suspicious values, unexpected JavaScript code, or settings that were not intentionally modified

A user is affected if the Easy PayPal Gift Certificate plugin is installed with version 1.2.3 or lower and the wpppgc_plugin_options function lacks proper nonce validation, allowing potential unauthorized settings changes via forged admin requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patch or update to the latest plugin version which includes proper nonce validation. Until a patch is available, review plugin settings pages for any unauthorized changes and monitor for malicious script injections.

Recommended fix Moderate confidence

Latest version available on WordPress plugin repository (version higher than 1.2.3)

  1. Check the WordPress plugin repository for Easy PayPal Gift Certificate for the latest version
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate Easy PayPal Gift Certificate plugin
  4. If current version is 1.2.3 or below, update to the latest available version
  5. Verify the update completes successfully
  6. Review plugin settings to ensure no unauthorized changes were made

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9592 — 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-9592 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