Vulnerability Scan Result
| Title: | ì ì¬ë ì ì¤í ì´ |
| Description: | ìëë¤ì¤ ë¸ëëì¤í ì´, ì¬ì°ëìí¸ ê³µì ì´í |
| ip_address | 203.245.12.108 |
| country | KR  |
| network_name | KT Corporation |
| asn | AS4766 |
| ip_address | 203.245.12.118 |
| country | KR |
| network_name | KT Corporation |
| asn | AS4766 |
| ip_address | 183.111.139.232 |
| country | KR |
| network_name | KT Corporation |
| asn | AS4766 |
| ip_address | 210.114.23.164 |
| country | KR |
| network_name | KT Corporation |
| asn | AS4766 |
80/tcp | http | OpenResty web app server - |
443/tcp | https | openresty - |
| Software / Version | Category |
|---|---|
| Naver Analytics | Analytics |
| Babel | Miscellaneous |
| cdnjs | CDN |
| jQuery CDN | CDN |
| Kakao | Miscellaneous |
| Facebook Pixel 2.9.313 | Analytics |
| Firebase | Databases, Development |
| Font Awesome | Font scripts |
| Google Font API | Font scripts |
| Froala Editor 2+ | Rich text editors |
| crypto-js | JavaScript libraries |
| core-js 3.45.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 3.6.0 | JavaScript libraries |
| Moment.js | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| OpenResty | Web servers |
| parcel | Miscellaneous |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| SWC | Miscellaneous |
| Swiper | JavaScript libraries |
| Unpkg | CDN |
| Vue.js | JavaScript frameworks |
| WordPress | CMS, Blogs |
| AMP | JavaScript frameworks |
| Cafe24 | Ecommerce |
| Cloudflare | CDN |
| CREMA | Personalisation, Reviews |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| Lodash 4.17.21 | JavaScript libraries |
| HSTS | Security |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-4800 | 8.1 | 0.00038 | 0.11381 | Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for the variable option in _.template but did not apply the same validation to options.imports key names. Both paths flow into the same Function() constructor sink. When an application passes untrusted input as options.imports key names, an attacker can inject default-parameter expressions that execute arbitrary code at template compilation time. Additionally, _.template uses assignInWith to merge imports, which enumerates inherited properties via for..in. If Object.prototype has been polluted by any other vector, the polluted keys are copied into the imports object and passed to Function(). Patches: Users should upgrade to version 4.18.0. Workarounds: Do not pass untrusted input as key names in options.imports. Only use developer-controlled, static key names. |
| CVE-2025-13465 | 6.9 | 0.00029 | 0.08338 | Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23 |
| CVE-2026-2950 | 6.5 | 0.00025 | 0.0705 | Impact: Lodash versions 4.17.23 and earlier are vulnerable to prototype pollution in the _.unset and _.omit functions. The fix for (CVE-2025-13465: https://github.com/lodash/lodash/security/advisories/GHSA-xxjr-mmjv-4gpg) only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype. The issue permits deletion of prototype properties but does not allow overwriting their original behavior. Patches: This issue is patched in 4.18.0. Workarounds: None. Upgrade to the patched version. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://athleisurestore.co.kr/order/basket.html | org_phpsess_id_1, basketcount_1, basketprice_1, atl_epcheck, atl_option | Set-Cookie: org_phpsess_id_1=69e6eumup67m04ljf0cr0854j6dmlra3 Set-Cookie: basketcount_1=0 Set-Cookie: basketprice_1=0%EC%9B%90 Set-Cookie: atl_epcheck=1 Set-Cookie: atl_option=1%2C1%2CH |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://athleisurestore.co.kr/order/basket.html | ECSESSID | Set-Cookie: .athleisurestore.co.kr |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://athleisurestore.co.kr/order/basket.html | basketcount_1, basketprice_1, atl_epcheck, atl_option | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: basketcount_1=0 Set-Cookie: basketprice_1=0%EC%9B%90 Set-Cookie: atl_epcheck=1 Set-Cookie: atl_option=1%2C1%2CH |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://athleisurestore.co.kr/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Naver Analytics | Analytics |
| Babel | Miscellaneous |
| cdnjs | CDN |
| jQuery CDN | CDN |
| Kakao | Miscellaneous |
| Facebook Pixel 2.9.313 | Analytics |
| Firebase | Databases, Development |
| Font Awesome | Font scripts |
| Google Font API | Font scripts |
| Froala Editor 2+ | Rich text editors |
| crypto-js | JavaScript libraries |
| core-js 3.45.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 3.6.0 | JavaScript libraries |
| Moment.js | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| OpenResty | Web servers |
| parcel | Miscellaneous |
| PHP | Programming languages |
| DoubleClick Floodlight | Advertising |
| SWC | Miscellaneous |
| Swiper | JavaScript libraries |
| Unpkg | CDN |
| Vue.js | JavaScript frameworks |
| WordPress | CMS, Blogs |
| AMP | JavaScript frameworks |
| Cafe24 | Ecommerce |
| Cloudflare | CDN |
| CREMA | Personalisation, Reviews |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| Lodash 4.17.21 | JavaScript libraries |
| HSTS | Security |
| Cart Functionality | Ecommerce |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.
Risk description
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://athleisurestore.co.kr/product/신제품-아디다스-컴뱃스포츠-트레이닝복-세트-tr100/1195/category | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Suspicious comment admin found in: |
Vulnerability description
We have discovered that the target application's code contains suspicious comments that may be related to potential bugs, incomplete functionality, or weaknesses. These comments often arise during development and testing phases but are inadvertently left in the code.
Risk description
The risk exists that attackers could analyze these comments to identify vulnerabilities or weaknesses in the application. While comments themselves do not directly lead to security breaches, they may guide attackers to focus their efforts on specific parts of the application, potentially uncovering and exploiting vulnerabilities.
Recommendation
Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.
Classification
| CWE | CWE-546 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://athleisurestore.co.kr/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Email Address: jkmonster.tk@gmail.com support@cre.ma help@goodymall.co.kr |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns1.cafe24.co.kr, ns2.cafe24.co.kr, ns2.cafe24.com, ns1.cafe24.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Firebase | Databases, Development |
| MySQL | Databases |
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Vue.js | JavaScript frameworks |
| AMP | JavaScript frameworks |
| OpenResty | Web servers |
| Cloudflare | CDN |
| Unpkg | CDN |
| Swiper | JavaScript libraries |
| Naver Analytics | Analytics |
| jQuery CDN | CDN |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.313 | Analytics |
| CREMA | Personalisation, Reviews |
| cdnjs | CDN |
| Google Analytics GA4 | Analytics |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Firebase | Databases, Development |
| MySQL | Databases |
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Vue.js | JavaScript frameworks |
| AMP | JavaScript frameworks |
| OpenResty | Web servers |
| Cloudflare | CDN |
| Unpkg | CDN |
| Swiper | JavaScript libraries |
| Naver Analytics | Analytics |
| jQuery CDN | CDN |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Facebook Pixel 2.9.313 | Analytics |
| CREMA | Personalisation, Reviews |
| cdnjs | CDN |
| Google Analytics GA4 | Analytics |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Operating System | Accuracy |
|---|---|
| OpenBSD 4.3 | 87% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| athleisurestore.co.kr | A | IPv4 address | 203.245.12.108 |
| athleisurestore.co.kr | A | IPv4 address | 210.114.23.164 |
| athleisurestore.co.kr | A | IPv4 address | 183.111.139.232 |
| athleisurestore.co.kr | A | IPv4 address | 203.245.12.118 |
| athleisurestore.co.kr | NS | Name server | ns1.cafe24.co.kr |
| athleisurestore.co.kr | NS | Name server | ns2.cafe24.co.kr |
| athleisurestore.co.kr | NS | Name server | ns2.cafe24.com |
| athleisurestore.co.kr | NS | Name server | ns1.cafe24.com |
| athleisurestore.co.kr | SOA | Start of Authority | athleisurestore.co.kr. postmaster.athleisurestore.co.kr. 20231114 10800 3600 3600000 43200 |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.