Beomps Korea Postcode Search Security & Risk Analysis

wordpress.org/plugins/beomps-korea-postcode-search

우커머스의 한국형 도로명 주소/우편번호 검색 플러그인 입니다.

90 active installs v3.4 PHP + WP 4.2.3+ Updated Nov 15, 2017
addressbeompskoreapostcodesearch
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Beomps Korea Postcode Search Safe to Use in 2026?

Generally Safe

Score 85/100

Beomps Korea Postcode Search 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 plugin "beomps-korea-postcode-search" v3.4 exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points indicates a minimal attack surface. Furthermore, the code signals show no dangerous functions, no raw SQL queries, no file operations, and no external HTTP requests, all of which are positive indicators for security. The presence of capability checks is also a good sign.

However, a significant concern arises from the output escaping analysis. With 1 total output and 0% properly escaped, this presents a notable risk of Cross-Site Scripting (XSS) vulnerabilities. While the taint analysis shows no critical or high severity flows, the lack of proper output escaping means any data processed by the plugin that is then displayed to the user could be manipulated. The vulnerability history being clean is a positive sign, suggesting a history of secure development, but it does not mitigate the immediate risk posed by unescaped output.

In conclusion, the plugin's strengths lie in its limited attack surface and avoidance of common dangerous coding practices. The major weakness is the lack of output escaping, which is a critical security oversight that could lead to XSS vulnerabilities. Users should be aware of this risk until it is addressed by the plugin developers.

Key Concerns

  • 100% of outputs are not properly escaped
Vulnerabilities
None known

Beomps Korea Postcode Search Security Vulnerabilities

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

Beomps Korea Postcode Search Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

Beomps Korea Postcode Search Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
filterwoocommerce_checkout_fieldsbeomps-korea-post-search.php:12
filterwoocommerce_billing_fieldsbeomps-korea-post-search.php:68
filterwoocommerce_shipping_fieldsbeomps-korea-post-search.php:79
actioninitbeomps-korea-post-search.php:93
actionwp_enqueue_scriptsbeomps-korea-post-search.php:111
actionadmin_menubeomps-korea-post-search.php:192
actionadmin_initbeomps-korea-post-search.php:359
Maintenance & Trust

Beomps Korea Postcode Search Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedNov 15, 2017
PHP min version
Downloads11K

Community Trust

Rating100/100
Number of ratings11
Active installs90
Developer Profile

Beomps Korea Postcode Search Developer Profile

beomps

1 plugin · 90 total installs

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

How We Detect Beomps Korea Postcode Search

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/beomps-korea-postcode-search/postcode.v2.js
Script Paths
https://spi.maps.daum.net/imap/map_js_init/postcode.v2.jshttps://ssl.daumcdn.net/dmaps/map_js_init/postcode.v2.jshttp://ssl.daumcdn.net/dmaps/map_js_init/postcode.v2.js

HTML / DOM Fingerprints

CSS Classes
btn
Data Attributes
onclick="openDaumPostcode()"onclick="openDaumPostcode2()"
JS Globals
daum
FAQ

Frequently Asked Questions about Beomps Korea Postcode Search