dbcve.org
Simple Signup FormWordPress extension · Modalsurvey

CVE-2024-13595

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 1.6.5 or later.
See remediation →
71/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 Simple Signup Form plugin for WordPress is vulnerable to SQL Injection via the 'id' attribute of the 'ssf' shortcode in all versions up to, and including, 1.6.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Simple Signup Form WordPress plugin is vulnerable to SQL Injection in versions up to 1.6.5. The 'id' parameter in the 'ssf' shortcode is not properly escaped and the SQL query lacks prepared statements, allowing authenticated attackers with Contributor-level access or higher to inject arbitrary SQL queries and extract sensitive database information.

MitigationUpdate to the latest version of the plugin when available, or if no patch exists, remove the plugin entirely. Until fixed, limit or audit contributor-level user accounts.

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
Simple Signup FormWordPress extension
Affected:<= 1.6.5

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 plugin installation
    Navigate to WordPress admin dashboard > Plugins. Look for 'Simple Signup Form' or 'Modalsurvey Simple Signup Form' in the installed plugins list.
    Affected if The plugin is present in the plugins list
  2. Identify installed version
    In the Plugins page, click on the plugin name or view details to see the installed version number. Compare it to the affected range: <= 1.6.5
    Affected if The installed version is 1.6.5 or lower
  3. Check for vulnerable shortcode usage
    Search your WordPress posts, pages, and widgets for the '[ssf' shortcode. This can be done via WordPress admin > Posts/Pages, or by querying the wp_posts database table for post_content containing 'ssf'.
    Affected if The '[ssf' shortcode is present in any published content
  4. Verify contributor-level access exists
    In WordPress admin > Users, review the user list. Check if any accounts have the 'Contributor' role or higher (Editor, Author, Administrator).
    Affected if There are one or more users with Contributor-level access or above

A user is affected if the Simple Signup Form plugin version is 1.6.5 or lower, the '[ssf' shortcode is in use, and any Contributor-level or higher user account 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
Upgrade available Upgrade to a release after 1.6.5
Interim mitigation

Update to the latest version of the plugin when available, or if no patch exists, remove the plugin entirely. Until fixed, limit or audit contributor-level user accounts.

Recommended fix Moderate confidence

Simple Signup Form version > 1.6.5 (check WordPress plugin repository for latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the Simple Signup Form plugin
  4. Check if the current version is 1.6.5 or lower
  5. If vulnerable, click Update Now to upgrade to the latest version
  6. Verify the update completes successfully
  7. Test the ssf shortcode functionality to ensure the plugin still works correctly after the update

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

Fix this in Simple Signup Form Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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