Vulnerability Scan Result
| Title: | No title found |
| Description: | No description found |
| ip_address | 169.150.247.33 |
| country | DE  |
| network_name | Datacamp Limited |
| asn | AS60068 |
22/tcp | ssh | OpenSSH 9.6p1 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Bunny | CDN |
| Bunny Fonts | Font scripts |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Bunny | CDN |
| Bunny Fonts | Font scripts |
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
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
Vulnerability description
Website is accessible.
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.
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2025-5062 | 6.1 | 0.00422 | 0.61285 | No | The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2024-9944 | 5.3 | 0.00207 | 0.43144 | No | The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0.2. This is due to the plugin not properly neutralizing HTML elements from submitted order forms. This makes it possible for unauthenticated attackers to inject arbitrary HTML that will render when the administrator views order form submissions. |
| CVE-2023-52222 | 4.3 | 0.00199 | 0.42268 | No | Cross-Site Request Forgery (CSRF) vulnerability in Automattic WooCommerce.This issue affects WooCommerce: from n/a through 8.2.2. |
Vulnerability description
Vulnerabilities found for WooCommerce 8.2.1
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; 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
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-10-14 21:10 EEST Nmap scan report for 930f4da2.delivery.rocketcdn.me (138.199.37.229) Host is up (0.013s latency). rDNS record for 138.199.37.229: 138-199-37-229.bunnyinfra.net
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 1.24 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2025-5062 | 6.1 | 0.00422 | 0.61285 | No | The WooCommerce plugin for WordPress is vulnerable to PostMessage-Based Cross-Site Scripting via the 'customize-store' page in all versions up to, and including, 9.4.2 due to insufficient input sanitization and output escaping on PostMessage data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. |
| CVE-2024-9944 | 5.3 | 0.00207 | 0.43144 | No | The WooCommerce plugin for WordPress is vulnerable to HTML Injection in all versions up to, and including, 9.0.2. This is due to the plugin not properly neutralizing HTML elements from submitted order forms. This makes it possible for unauthenticated attackers to inject arbitrary HTML that will render when the administrator views order form submissions. |
| CVE-2023-52222 | 4.3 | 0.00199 | 0.42268 | No | Cross-Site Request Forgery (CSRF) vulnerability in Automattic WooCommerce.This issue affects WooCommerce: from n/a through 8.2.2. |
Vulnerability description
Vulnerabilities found for WooCommerce 8.2.1
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; 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
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns1.bunnydns.com, ns2.bunnydns.com, ns3.bunnydns.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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| 930f4da2.delivery.rocketcdn.me | A | IPv4 address | 138.199.37.231 |
| 930f4da2.delivery.rocketcdn.me | NS | Name server | ns1.bunnydns.com |
| 930f4da2.delivery.rocketcdn.me | NS | Name server | ns2.bunnydns.com |
| 930f4da2.delivery.rocketcdn.me | NS | Name server | ns3.bunnydns.com |
| 930f4da2.delivery.rocketcdn.me | MX | Mail server | 1 ASPMX.L.GOOGLE.COM |
| 930f4da2.delivery.rocketcdn.me | MX | Mail server | 5 ALT1.ASPMX.L.GOOGLE.COM |
| 930f4da2.delivery.rocketcdn.me | MX | Mail server | 5 ALT2.ASPMX.L.GOOGLE.COM |
| 930f4da2.delivery.rocketcdn.me | MX | Mail server | 10 ALT3.ASPMX.L.GOOGLE.COM |
| 930f4da2.delivery.rocketcdn.me | MX | Mail server | 10 ALT4.ASPMX.L.GOOGLE.COM |
| 930f4da2.delivery.rocketcdn.me | SOA | Start of Authority | ns1.bunnydns.com. hostmaster.bunnydns.com. 2021497770 7200 900 1209600 86400 |
| 930f4da2.delivery.rocketcdn.me | TXT | Text record | "google-site-verification=g4uJHVKRsz3YNsU1tqAZOjg9QgO3twmIFeQd3aJrikQ" |
| 930f4da2.delivery.rocketcdn.me | CNAME | Canonical name | b-cdn.net |
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 |
|---|---|
| FreeBSD 12.0-RELEASE | 86% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Slider Revolution 6.6.17 | Widgets, Photo galleries |
| Cart Functionality | Ecommerce |
| Emotion | JavaScript frameworks, Development |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| Contact Form 7 5.8.1 | WordPress plugins, Form builders |
| Bunny | CDN |
| Woodmart | WordPress themes |
| WP Rocket | Caching, WordPress plugins |
| WooCommerce 8.2.1 | Ecommerce, WordPress plugins |
| Jetpack | WordPress plugins |
| Elementor 3.16.6 | Page builders, WordPress plugins |
| Yoast SEO 21.4 | SEO, WordPress plugins |
| WooCommerce Multilingual 5.2.0 | WordPress plugins, Translation |
| Site Kit 1.163.0 | Analytics, WordPress plugins |
| Performance Lab 2.7.0 | WordPress plugins, Performance |
| Trustpilot | Reviews |
| Swiper | JavaScript libraries |
| reCAPTCHA | Security |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| GoAffPro | Affiliate programs |
| Cloudflare | CDN |
| Priority Hints | Performance |
| Preact | JavaScript libraries |
| Google Font API | Font scripts |
| Font Awesome 4.7.0 | Font scripts |
| cdnjs | CDN |
| RSS | Miscellaneous |
| Open Graph | Miscellaneous |
| Bunny Fonts | Font scripts |
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 |
| Slider Revolution 6.6.17 | Widgets, Photo galleries |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 5 | UI frameworks |
| Contact Form 7 5.8.1 | WordPress plugins, Form builders |
| Nginx | Web servers, Reverse proxies |
| Bunny Fonts | Font scripts |
| Bunny | CDN |
| WooCommerce 8.2.1 | Ecommerce, WordPress plugins |
| Jetpack | WordPress plugins |
| Elementor 3.16.6 | Page builders, WordPress plugins |
| Yoast SEO 21.4 | SEO, WordPress plugins |
| WooCommerce Multilingual 5.2.0 | WordPress plugins, Translation |
| Site Kit 1.163.0 | Analytics, WordPress plugins |
| Performance Lab 2.7.0 | WordPress plugins, Performance |
| Trustpilot | Reviews |
| Swiper | JavaScript libraries |
| reCAPTCHA | Security |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| GoAffPro | Affiliate programs |
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.