Vulnerability Scan Result
| Title: | خاتون اصفهان |
| Description: | **«سلام زیبایی! به دنیای خاتون خوش آمدی 🌸»* میدانیم که مراقبت از پوست و زیبایی و مو ، فقط یک روتین نیست؛ بلکه نوعی عشق ورزیدن به خودتان است. در فروشگاه «خاتون»، ما با دقت و وسواس، بهترین و معتبرترین برندهای آرایشی و بهداشتی را برای شما گلچین کردهایم. دغدغه ما؟ فقط یک چیز: اینکه با خیالی آسوده، بهترینها را برای خودتان بخرید. چون اصالتِ کالای ما، تضمینِ زیبایی شماست. > 🛍️ *همین حالا با ما همراه شوید و تجربهای متفاوت از خرید داشته باشید.* |
| ip_address | 185.53.143.214 |
| country | IR  |
| network_name | Mobinhost |
| asn | AS208555 |
22/tcp | ssh | OpenSSH 8.2p1 Ubuntu 4ubuntu0.9 |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Emotion | JavaScript frameworks, Development |
| eNamad | Miscellaneous |
| Font Awesome | Font scripts |
| Goober | JavaScript libraries |
| jQuery 3.5.0 | JavaScript libraries |
| Mixin | Ecommerce |
| MUI | UI frameworks |
| Next.js 14.2.35 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Next.js App Router | JavaScript frameworks, Web servers |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Sentry | Issue trackers |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| Format | CMS |
| HSTS | Security |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-27980 | 6.9 | 0.00022 | 0.06439 | Next.js is a React framework for building full-stack web applications. Starting in version 10.0.0 and prior to version 16.1.7, the default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth. An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. This is fixed in version 16.1.7 by adding an LRU-backed disk cache with `images.maximumDiskCacheSize`, including eviction of least-recently-used entries when the limit is exceeded. Setting `maximumDiskCacheSize: 0` disables disk caching. If upgrading is not immediately possible, periodically clean `.next/cache/images` and/or reduce variant cardinality (e.g., tighten values for `images.localPatterns`, `images.remotePatterns`, and `images.qualities`). |
| CVE-2026-29057 | 6.3 | 0.00031 | 0.09136 | Next.js is a React framework for building full-stack web applications. Starting in version 9.5.0 and prior to versions 15.5.13 and 16.1.7, when Next.js rewrites proxy traffic to an external backend, a crafted `DELETE`/`OPTIONS` request using `Transfer-Encoding: chunked` could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes. An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel. The vulnerability originated in an upstream library vendored by Next.js. It is fixed in Next.js 15.5.13 and 16.1.7 by updating that dependency’s behavior so `content-length: 0` is added only when both `content-length` and `transfer-encoding` are absent, and `transfer-encoding` is no longer removed in that code path. If upgrading is not immediately possible, block chunked `DELETE`/`OPTIONS` requests on rewritten routes at the edge/proxy, and/or enforce authentication/authorization on backend routes. |
| CVE-2025-59471 | 5.9 | 0.00027 | 0.0788 | A denial of service vulnerability exists in self-hosted Next.js applications that have `remotePatterns` configured for the Image Optimizer. The image optimization endpoint (`/_next/image`) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that `remotePatterns` is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain. Strongly consider upgrading to 15.5.10 or 16.1.5 to reduce risk and prevent availability issues in Next applications. |
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 | Evidence |
|---|---|
| https://khatoonbeautyesf.ir/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Emotion | JavaScript frameworks, Development |
| eNamad | Miscellaneous |
| Font Awesome | Font scripts |
| Goober | JavaScript libraries |
| jQuery 3.5.0 | JavaScript libraries |
| Mixin | Ecommerce |
| MUI | UI frameworks |
| Next.js 14.2.35 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Next.js App Router | JavaScript frameworks, Web servers |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Sentry | Issue trackers |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| Format | CMS |
| 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).
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 |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| khatoonbeautyesf.ir | A | IPv4 address | 185.53.143.214 |
| khatoonbeautyesf.ir | NS | Name server | ns1.mxndns.com |
| khatoonbeautyesf.ir | NS | Name server | ns2.mxndns.com |
| khatoonbeautyesf.ir | SOA | Start of Authority | ns1.mxndns.com. hostmaster.arvancloud.ir. 1778589895 86400 7200 604800 7200 |
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.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 5.0 - 5.4 | 96% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Mixin | Ecommerce |
| Format | CMS |
| Material UI | UI frameworks |
| React | JavaScript frameworks |
| HSTS | Security |
| eNamad | Miscellaneous |
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.