SafetyformsWordPress extension · Henriquerodrigues
CVE-2024-49615
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Henrique Rodrigues SafetyForms safetymails-forms allows Blind SQL Injection.This issue affects SafetyForms: from n/a through <= 1.0.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the SafetyForms safetymails-forms WordPress plugin allows attackers to execute Blind SQL Injection by tricking authenticated users into submitting malicious requests. The lack of proper CSRF protection combined with unsanitized SQL queries enables remote attackers to extract sensitive data from the database.
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
SafetyformsWordPress extension
<= 1.0.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify SafetyForms plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder containing 'safetymails-forms' or 'safetyforms', or view installed plugins in WordPress admin under Plugins > Installed PluginsAffected if The plugin named 'Henriquerodrigues Safetyforms' or 'SafetyForms safetymails-forms' appears in the plugin list
-
Check installed plugin versionIn WordPress admin, click on the plugin to view its details and locate the version number, or open the main plugin PHP file (e.g., safetymails-forms.php) and read the 'Version' header in the plugin comment blockAffected if The version is 1.0.0 or lower (the vulnerable version range is <= 1.0.0)
-
Confirm plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify the SafetyForms plugin status shows as 'Active'Affected if The plugin is active and processing form submissions
-
Identify if forms are configured and accepting submissionsCheck if any forms created with SafetyForms are configured and accessible on the site. Look for frontend form pages or check the plugin's form management interface in WordPress adminAffected if The plugin has active forms that accept user submissions, which is required for the CSRF-triggered SQL injection to be exploitable
You are affected if the Henriquerodrigues Safetyforms plugin version 1.0.0 or lower is installed, active, and configured with forms that accept submissions, enabling CSRF-triggered blind SQL injection.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to the latest patched version of SafetyForms plugin. Additionally, implement anti-CSRF tokens on all form submissions and use parameterized queries or prepared statements to prevent SQL injection.
Fix this in Safetyforms
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49615 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49615 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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