MyPress Security & Risk Analysis

wordpress.org/plugins/my-press

Connect WordPress with MyBB. Everytime a user registers in your MyBB Forum, he will also be registered in WordPress.

10 active installs v1.01 PHP + WP 3.0.1+ Updated Unknown
mybb
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is MyPress Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "my-press" plugin v1.01 demonstrates a concerning lack of basic security practices, despite having no reported vulnerabilities or a large attack surface. The static analysis reveals that none of the observed SQL queries use prepared statements, and all observed output is not properly escaped. This combination poses a significant risk of SQL injection and Cross-Site Scripting (XSS) vulnerabilities, as user-supplied data can be directly injected into database queries or rendered in the browser without sanitization. While the plugin currently has no known CVEs and a zero attack surface, this can be misleading. The absence of reported vulnerabilities might be due to its obscurity or the fact that its inherent weaknesses haven't been discovered or exploited yet. The significant findings in SQL query and output escaping practices overshadow the lack of a large attack surface or known CVEs, suggesting a critical need for code review and remediation.

Key Concerns

  • 100% of SQL queries do not use prepared statements
  • 100% of outputs are not properly escaped
  • No capability checks found
  • No nonce checks found
Vulnerabilities
None known

MyPress Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

MyPress Code Analysis

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

SQL Query Safety

0% prepared1 total queries

Output Escaping

0% escaped1 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
mypress_settings (mypress.php:39)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

MyPress Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menumypress.php:36
actionwp_loginmypress.php:67
actionwp_logoutmypress.php:82
Maintenance & Trust

MyPress Maintenance & Trust

Maintenance Signals

WordPress version tested4.5.33
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

MyPress Developer Profile

Grork

1 plugin · 10 total installs

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

How We Detect MyPress

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/my-press/

HTML / DOM Fingerprints

CSS Classes
wrapform-tableregular-textbuttonbutton-primary
HTML Comments
Admin settingsCoreCore - MyBB Inclusion
Data Attributes
for="mybb_path"id="mybb_path"name="mybb_path"id="submit"
FAQ

Frequently Asked Questions about MyPress