amoForms Security & Risk Analysis

wordpress.org/plugins/amoforms

Create forms and manage submissions easily with a simple interface. Contact forms, subscription forms, or other forms for WordPress. Absolutely FREE!

300 active installs v3.1.19 PHP + WP 4.0+ Updated Nov 13, 2019
adminformpostshortcodewidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is amoForms Safe to Use in 2026?

Generally Safe

Score 85/100

amoForms has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 6yr ago
Risk Assessment

The "amoforms" v3.1.19 plugin presents a mixed security posture. While it has a historically clean record with zero known CVEs, indicating good general maintenance and security awareness from the developers, the static analysis reveals several concerning code practices. The presence of the `exec()` function, even if not directly tied to an exploitable flow in this analysis, is a significant red flag as it can be a gateway to command injection vulnerabilities if not handled with extreme caution and rigorous sanitization. Furthermore, a very low percentage of output escaping (2%) is a critical weakness, suggesting a high risk of cross-site scripting (XSS) vulnerabilities where user-supplied data might be rendered directly in the browser without proper encoding. The taint analysis, while showing no critical or high severity flows, analyzed a very small number of flows (3), making its findings potentially incomplete.

Key Concerns

  • Use of dangerous function 'exec'
  • Low output escaping percentage (2%)
  • Taint analysis flow count is very low
Vulnerabilities
None known

amoForms Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

amoForms Release Timeline

v3.1.19Current
vv3.1.19
v3.1.18
v3.1.17
v3.1.16
v3.1.15
v3.1.14
v3.1.13
v3.1.12
v3.1.11
v3.1.10
v3.1.9
v3.1.8
v3.1.7
v3.1.6
v3.1.5
v3.1.4
v3.1.3
v3.1.1
v3.1.0
Code Analysis
Analyzed Mar 16, 2026

amoForms Code Analysis

Dangerous Functions
1
Raw SQL Queries
16
17 prepared
Unescaped Output
132
3 escaped
Nonce Checks
0
Capability Checks
1
File Operations
16
External Requests
7
Bundled Libraries
1

Dangerous Functions Found

execexec($cmd);classes\Vendor\Raven\Client.php:666

Bundled Libraries

TinyMCE

SQL Query Safety

52% prepared33 total queries

Output Escaping

2% escaped135 total outputs
Data Flows · Security
3 unsanitized

Data Flow Analysis

3 flows3 with unsanitized paths
dismiss_notice_action (classes\Controllers\Settings.php:1181)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

amoForms Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[amoforms] classes\Libs\Shortcodes\Manager.php:40
WordPress Hooks 10
filterwp_handle_upload_prefilterclasses\Controllers\Settings.php:424
filtertiny_mce_before_initclasses\Libs\Filters\TinyMCE.php:26
filtermce_external_pluginsclasses\Libs\Filters\TinyMCE.php:30
filtermce_buttonsclasses\Libs\Filters\TinyMCE.php:31
filtermedia_buttonsclasses\Libs\Hooks\MediaButtons\AddForm.php:19
actionadmin_footerclasses\Libs\Hooks\MediaButtons\AddForm.php:20
actioninitclasses\Libs\Hooks\PreviewPage\ManagePage.php:20
filterthe_contentclasses\Libs\Hooks\PreviewPage\PutForm.php:26
actionadmin_menuclasses\Router.php:391
filteradmin_footer_textviews\other\notice.php:12
Maintenance & Trust

amoForms Maintenance & Trust

Maintenance Signals

WordPress version tested5.2.24
Last updatedNov 13, 2019
PHP min version
Downloads905K

Community Trust

Rating86/100
Number of ratings52
Active installs300
Developer Profile

amoForms Developer Profile

BaggerMAN

1 plugin · 300 total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect amoForms

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about amoForms