CVE-2025-15441
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 · uneditedThe Form Maker by 10Web WordPress plugin before 1.15.38 does not properly prepare SQL queries when the "MySQL Mapping" feature is in use, which could make SQL Injection attacks possible in certain contexts.
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 confidenceThe Form Maker by 10Web WordPress plugin before version 1.15.38 contains a SQL injection vulnerability in the MySQL Mapping feature. The plugin fails to properly prepare SQL queries, allowing attackers to inject malicious SQL commands through this specific feature.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionNavigate to WordPress Admin > Plugins and locate Form Maker by 10Web, or inspect the plugin header in wp-content/plugins/form-maker/readme.txt or the main plugin PHP file for the 'Version' declarationAffected if The displayed version is lower than 1.15.38 (for example, 1.15.37, 1.15.36, etc.)
-
Verify MySQL Mapping feature existenceIn the WordPress admin, go to Form Maker settings or look for a MySQL Mapping/Mapping section within the plugin menu. This feature allows connecting forms to external MySQL databasesAffected if The MySQL Mapping feature is present and configurable in the plugin interface, indicating the vulnerable code is installed
-
Confirm database connection configurationCheck if any MySQL database connections have been created in Form Maker settings, or examine the wp_options table for form_maker_mysql_* option names that store mapping configurationsAffected if There are active MySQL mapping configurations saved in the plugin, meaning the vulnerable feature is in use
You are affected if the Form Maker by 10Web plugin version is below 1.15.38 AND the MySQL Mapping feature is enabled or has been configured in your WordPress environment.
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.
dbcve · scopedUpdate the Form Maker by 10Web plugin to version 1.15.38 or later to obtain the patched code that properly prepares SQL queries in the MySQL Mapping feature.
1.15.38 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Form Maker by 10Web' in the plugin list
- Check the current version number
- If the installed version is below 1.15.38, click 'Update Now' to upgrade to the latest version
- Alternatively, download version 1.15.38 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
- After updating, verify the version number reflects 1.15.38 or higher
- If the MySQL Mapping feature was in use, test that functionality to confirm it still works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15441 — 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-2025-15441 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