WP OAuth Integration Security & Risk Analysis

wordpress.org/plugins/wp-oauth-integration

Create and Manage an OAuth 2.0 Integration powered by WordPress.

10 active installs v0.1.3 PHP + WP 4.9.1+ Updated Jan 12, 2018
oauthoauth-provideroauth2oauth2-serviceprovider
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is WP OAuth Integration Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The "wp-oauth-integration" plugin version 0.1.3 exhibits a generally strong security posture based on the provided static analysis. The absence of known vulnerabilities, coupled with a complete lack of SQL queries executed without prepared statements, and zero taint flows of critical or high severity, are all positive indicators. The plugin also demonstrates good practices by including nonce and capability checks for its limited entry points. The minimal attack surface and lack of file operations or external HTTP requests further contribute to its perceived security.

However, there are minor areas for improvement. The output escaping is only 50% properly implemented, meaning there's a potential for unescaped output, which could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is displayed without proper sanitization. While the current version has no known vulnerabilities, this could be due to its early stage (v0.1.3) or limited adoption. The plugin's vulnerability history is clean, which is a good sign, but ongoing monitoring is always recommended, especially for plugins with a limited version history.

In conclusion, "wp-oauth-integration" v0.1.3 appears to be a secure plugin with a commendable approach to many security best practices. The primary concern is the partial output escaping, which warrants attention. The lack of any historical vulnerabilities is a strength, but continued vigilance and updates are essential as the plugin matures and its attack surface potentially expands.

Key Concerns

  • Only 50% of outputs are properly escaped
Vulnerabilities
None known

WP OAuth Integration Security Vulnerabilities

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

WP OAuth Integration Code Analysis

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

Output Escaping

50% escaped2 total outputs
Attack Surface

WP OAuth Integration Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionadmin_noticesincludes\class-wp-oauth-integration-main.php:119
Maintenance & Trust

WP OAuth Integration Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedJan 12, 2018
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

WP OAuth Integration Developer Profile

Samer Bechara

8 plugins · 260 total installs

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

How We Detect WP OAuth Integration

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-oauth-integration/css/wp-oauth-integration.css/wp-content/plugins/wp-oauth-integration/js/wp-oauth-integration.js
Script Paths
/wp-content/plugins/wp-oauth-integration/js/wp-oauth-integration.js
Version Parameters
wp-oauth-integration/css/wp-oauth-integration.css?ver=wp-oauth-integration/js/wp-oauth-integration.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about WP OAuth Integration