Android Appmaker Security & Risk Analysis

wordpress.org/plugins/android-appmaker

Mit diesem Plugin kannst du für deine Seite eine Android-App erstellen. iOS Apps können auf Anfrage erstellt werden. Nach wenigen Klicks sind deine In …

10 active installs v4.0 PHP + WP 5.0+ Updated May 2, 2021
android-appapp-erstellenapp-selbst-erstelleneigene-appios-app
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Android Appmaker Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 5yr ago
Risk Assessment

The plugin 'android-appmaker' v4.0 exhibits a generally strong security posture based on the provided static analysis. The complete absence of identified CVEs and a clean vulnerability history are positive indicators. Notably, the plugin boasts a zero attack surface in terms of AJAX handlers, REST API routes, shortcodes, and cron events, which significantly reduces potential entry points for attackers. Furthermore, all SQL queries utilize prepared statements, and there are no file operations or external HTTP requests, further mitigating common attack vectors. The presence of a capability check, while only one, is also a good practice.

However, a significant concern arises from the output escaping. With 12 total outputs and only 8% properly escaped, a substantial number of outputs are likely vulnerable to cross-site scripting (XSS) attacks. This is a critical weakness that attackers could exploit to inject malicious scripts into the site. The lack of nonce checks is also a potential concern, especially if any of the limited entry points, despite being listed as zero, were to be indirectly accessed or if future updates introduce such entry points without adequate protection.

In conclusion, while the plugin has successfully avoided known vulnerabilities and has a minimal attack surface, the poor output escaping represents a significant and exploitable security flaw. The absence of nonce checks also warrants attention. Addressing the output escaping issue should be the top priority to improve the overall security of this plugin.

Key Concerns

  • Low output escaping percentage
Vulnerabilities
None known

Android Appmaker Security Vulnerabilities

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

Android Appmaker Release Timeline

v4.0Current
v3.9
v3.8
v3.7
v3.6
v3.5
v3.4
v3.3
v3.2
v3.1
v3.0
v2.9
v2.8
v2.7
v2.6
v2.5
v2.0
v1.2
Code Analysis
Analyzed Apr 16, 2026

Android Appmaker Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
11
1 escaped
Nonce Checks
0
Capability Checks
1
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

8% escaped12 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
my_plugin_options (appmaker.php:129)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Android Appmaker Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionadmin_menuappmaker.php:123
Maintenance & Trust

Android Appmaker Maintenance & Trust

Maintenance Signals

WordPress version tested5.7.15
Last updatedMay 2, 2021
PHP min version
Downloads7K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Android Appmaker Developer Profile

merqde

5 plugins · 100 total installs

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

How We Detect Android Appmaker

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/android-appmaker/appmaker-merq.js
Script Paths
/wp-content/plugins/android-appmaker/appmaker-merq.js
Version Parameters
android-appmaker/appmaker-merq.js?url=

HTML / DOM Fingerprints

Shortcode Output
<p>URL zum RSS-Feed: <b>/appmaker.php?rss=1&p=
FAQ

Frequently Asked Questions about Android Appmaker