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

CVE-2024-54414

HIGH · 7.1 CVSS v3.1 Published 2024-12-16
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 geoWP Geoportail Shortcode geoportail-shortcode allows Stored XSS.This issue affects Geoportail Shortcode: from n/a through <= 2.4.4.

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 geoWP Geoportail Shortcode plugin allows attackers to inject malicious scripts (Stored XSS) by tricking authenticated administrators into submitting crafted requests. The plugin fails to properly validate CSRF tokens and sanitize user input in its shortcode functionality.

MitigationImplement nonces for all form submissions and AJAX actions, and apply proper input sanitization and output encoding to prevent stored XSS attacks.

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 geoWP Geoportail Shortcode plugin is installed
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'geoWP Geoportail' or 'Geoportail Shortcode' to confirm the plugin is present and active
    Affected if The plugin is installed and active in WordPress
  2. Identify the installed plugin version
    In the Plugins list, click on the plugin name to view its details, or inspect the plugin header in wp-content/plugins/[plugin-folder]/geowp*.php to find the Version: x.x.x declaration
    Affected if The version number is lower than the latest patched version or falls within an unpatched range
  3. Check for active shortcode usage
    Search the WordPress database (wp_posts table) or content files for the shortcode tag used by this plugin, commonly [geowp] or similar, by querying: SELECT * FROM wp_posts WHERE post_content LIKE '%[geowp%'
    Affected if The shortcode is present in any post, page, or widget content
  4. Examine the shortcode syntax in post content, for example [geowp param1='value1'], and determine if any attributes accept user-controlled input such as location names, coordinates, or custom labels
    Affected if Shortcode attributes accept unsanitized user input that could be exploited for XSS
  5. Inspect plugin source for nonce validation
    If file access is available, open the main plugin PHP file and search for 'wp_nonce_field', 'wp_verify_nonce', or 'check_admin_referer' function calls within shortcode handler functions
    Affected if The plugin code lacks proper nonce validation for shortcode-related actions

The environment is affected if the geoWP Geoportail Shortcode plugin is installed, running an unpatched version, and has shortcodes in use with insufficient CSRF and input sanitization protections.

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

Implement nonces for all form submissions and AJAX actions, and apply proper input sanitization and output encoding to prevent stored XSS attacks.

Recommended fix Moderate confidence

Latest version newer than 2.4.4 (check WordPress plugin repository for current release)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Update the geoWP Geoportail Shortcode plugin to the latest available version from the WordPress plugin repository.
  3. 3. If the latest version is not available yet, consider temporarily disabling the plugin until an update is released.
  4. 4. After updating, verify the plugin is working correctly and test the functionality that was previously using the shortcode.
  5. 5. Consider implementing additional CSRF protection at the server level using anti-CSRF tokens if the plugin update does not fully address the vulnerability.
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA4.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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