Classipress SMS Security & Risk Analysis

wordpress.org/plugins/classipress-sms

Send SMS to seller in ClassiPress Theme

10 active installs v1.1 PHP + WP 3.0+ Updated Aug 13, 2014
classipresssms
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Classipress SMS Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The classipress-sms v1.1 plugin exhibits a concerning security posture primarily due to a lack of authentication checks on its exposed entry points. With two AJAX handlers identified, both of which lack authorization checks, an attacker could potentially trigger these functions without proper validation, leading to unintended actions or information disclosure. While the code shows good practices in other areas, such as using prepared statements for all SQL queries and the absence of recorded vulnerability history, these strengths are overshadowed by the critical deficiency in securing its AJAX endpoints. The plugin's attack surface is small, which is positive, but the unprotected nature of its entire entry point footprint is a significant risk.

The static analysis reveals no dangerous functions, no raw SQL queries, and all output is properly escaped, which are all positive signs. However, the absence of nonce checks and capability checks on the AJAX handlers is a major red flag. The vulnerability history being clear is a good sign, suggesting a lack of past exploitable issues, but it does not negate the current risks identified in the code. The overall conclusion is that while the plugin avoids common pitfalls like unescaped output and raw SQL, its failure to properly authenticate critical functions creates a direct and significant security risk that needs immediate attention.

Key Concerns

  • AJAX handlers without auth checks
  • AJAX handlers without nonce checks
  • AJAX handlers without capability checks
  • Low percentage of properly escaped output
Vulnerabilities
None known

Classipress SMS Security Vulnerabilities

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

Classipress SMS Release Timeline

No version history available.
Code Analysis
Analyzed Apr 16, 2026

Classipress SMS Code Analysis

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

Output Escaping

14% escaped14 total outputs
Attack Surface
2 unprotected

Classipress SMS Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_cps_send_smsclassipresssms.php:46
noprivwp_ajax_cps_send_smsclassipresssms.php:47
WordPress Hooks 4
actionappthemes_after_post_contentclassipresssms.php:45
filtercp_ad_details_fieldclassipresssms.php:50
actionadmin_menufunctions.php:12
actionadmin_initsettings.php:13
Maintenance & Trust

Classipress SMS Maintenance & Trust

Maintenance Signals

WordPress version tested3.9.40
Last updatedAug 13, 2014
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Classipress SMS Developer Profile

Rajesh Tandukar

1 plugin · 10 total installs

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

How We Detect Classipress SMS

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/classipress-sms/app-pencil.png/wp-content/plugins/classipress-sms/ajax-loading.gif

HTML / DOM Fingerprints

CSS Classes
classipress_smsclassipress_sms-linkclassipress_sms_loadingclassipress_sms_spanclassipress_sms_errorclassipress_sms_chars
Data Attributes
id="classipress_sms_messge_wrapper"id="classipress_sms_message"id="classipress_sms_chars"id="classipress_sms_submit"
JS Globals
cpsms_URL
REST Endpoints
/wp-json/cps_send_sms
FAQ

Frequently Asked Questions about Classipress SMS