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

CVE-2024-53723

HIGH · 7.1 CVSS v3.1 Published 2024-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 acbaltaci Google Plus Share and +1 Button google-plus-share-and-plusone-button allows Stored XSS.This issue affects Google Plus Share and +1 Button: from n/a through <= 1.0.

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

CSRF vulnerability in the Google Plus Share and +1 Button WordPress plugin (versions <=1.0) allows authenticated attackers to inject malicious JavaScript code through stored XSS by tricking administrators into visiting crafted links. The plugin lacks proper anti-CSRF token validation, enabling attackers to silently modify plugin settings and inject persistent malicious scripts.

MitigationReplace or remove the abandoned plugin (Google Plus API shut down in 2019); if continued use is required, implement nonce-based CSRF protection and output escaping on all user-controlled inputs before storing or rendering.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Verify plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Google Plus Share and +1 Button' or search for any plugin with 'Google Plus' or 'Google+' in the name. Check if it is installed.
    Affected if The Google Plus Share and +1 Button plugin is found in the plugins directory, regardless of activation status.
  2. Check plugin version
    In the installed plugins list, locate the version number displayed under the plugin name. Compare it against the affected range: versions 1.0 and below.
    Affected if The installed version is 1.0 or any version number indicating 1.0 or lower.
  3. Confirm plugin is active
    In the WordPress admin Plugins page, verify whether the plugin shows as 'Active' or 'Network Active'. The vulnerability requires an authenticated administrator to be exploitable.
    Affected if The plugin is currently active and accessible via the WordPress admin dashboard.
  4. Access plugin settings
    Navigate to the plugin settings page in WordPress admin (usually under Settings or a dedicated menu item named after the plugin). Look for fields related to Google+ sharing, buttons, or API configuration.
    Affected if The plugin settings page is accessible and contains user-controllable input fields where malicious scripts could be stored.

If the Google Plus Share and +1 Button plugin is installed at version 1.0 or below and is active with accessible settings, the environment is vulnerable to CVE-2024-53723 CSRF-induced stored XSS attacks.

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

Replace or remove the abandoned plugin (Google Plus API shut down in 2019); if continued use is required, implement nonce-based CSRF protection and output escaping on all user-controlled inputs before storing or rendering.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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