dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-10909

MEDIUM · 6.3 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 The Pojo Forms plugin for WordPress is vulnerable to arbitrary shortcode execution via form_preview_shortcode AJAX action in all versions up to, and including, 1.4.7. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with Subscriber-level access and above, to execute arbitrary shortcodes. This was partially fixed in version 1.4.8.

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 Pojo Forms WordPress plugin has an arbitrary shortcode execution vulnerability in the form_preview_shortcode AJAX action. Authenticated users with Subscriber-level access or higher can execute arbitrary shortcodes because the plugin does not properly validate input before passing it to do_shortcode().

MitigationUpdate to version 1.4.8 or later which includes a partial fix for this vulnerability.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Pojo Forms plugin is installed
    Check the WordPress plugin directory for 'pojo-forms' folder, or query the wp_plugins database table for the plugin entry
    Affected if The plugin folder 'pojo-forms' exists in /wp-content/plugins/ or is present in the plugins database table
  2. Check installed plugin version
    Read the main plugin file (e.g., pojo-forms.php) for the 'Version' header, or query the wp_options table for the 'pojo-forms_version' option
    Affected if The installed version is lower than 1.4.8 (e.g., 1.4.7, 1.4.6, etc.)
  3. Confirm plugin is active
    Query the wp_options table for the 'active_plugins' option, or check through WordPress admin > Plugins > Active plugins list
    Affected if 'pojo-forms/pojo-forms.php' appears in the active plugins list
  4. Check for authenticated users with Subscriber+ access
    Query the wp_usermeta table for users with wp_capabilities meta_value containing 'subscriber', 'contributor', 'author', 'editor', or 'administrator'
    Affected if At least one user account exists with Subscriber-level access or higher
  5. Verify AJAX endpoint is accessible
    Check if the WordPress AJAX handler is available at /wp-admin/admin-ajax.php and test if the 'form_preview_shortcode' action is registered by examining plugin code in includes/ajax.php or similar
    Affected if The plugin registers the 'form_preview_shortcode' AJAX action and the endpoint responds without authentication errors for low-privileged users

User is affected if Pojo Forms plugin versions below 1.4.8 are installed and active, and any authenticated user with Subscriber-level access or higher exists in the WordPress installation.

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

Update to version 1.4.8 or later which includes a partial fix for this vulnerability.

Recommended fix Moderate confidence

1.4.8 or later (latest available version)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Pojo Forms' in the plugin list
  4. If an update is available, click 'Update Now' to install 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 is running the latest version under Plugins > Installed Plugins

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