Vulnerability Scan Result
| Title: | Thihongcuc Ly - Merrell: Outdoor Schuhe und Bekleidung zum Wandern und ... |
| Description: | Offizielle Merrell Seite – Immer kostenloser ... Deine Anlaufstelle für das Neueste von Merrell Hiking Ganz ... da sind. Dolphin Jumping majestically ... |
| IP address | 172.67.169.8 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.21.27.68 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Animate.css | UI frameworks |
| Contact Form 7 5.6.1 | WordPress plugins, Form builders |
| Font Awesome | Font scripts |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| core-js 3.19.1 | JavaScript libraries |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| prettyPhoto | JavaScript libraries |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| ProfilePress 4.0.3 | WordPress plugins |
| Select2 | JavaScript libraries |
| WooCommerce 6.7.0 | Ecommerce, WordPress plugins |
| WordPress 5.9.3 | CMS, Blogs |
| wpBakery | Page builders, WordPress plugins |
| Cloudflare | CDN |
| Lodash 1.13.1 | JavaScript libraries |
| Max Mega Menu 2.9.7 | Widgets, WordPress plugins |
| RSS | Miscellaneous |
| Slider Revolution 6.5.19 | Widgets, Photo galleries |
| Cart Functionality | Ecommerce |
| Yoast SEO 19.4 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| Risk Level | CVSS | CVE | Summary | Affected software |
|---|---|---|---|---|
| 8.8 | CVE-2023-52222 | Cross-Site Request Forgery (CSRF) vulnerability in Automattic WooCommerce.This issue affects WooCommerce: from n/a through 8.2.2. | woocommerce 6.7.0 | |
| 6.1 | CVE-2022-43497 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | wordpress 5.9.3 | |
| 6.1 | CVE-2022-43500 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | wordpress 5.9.3 | |
| 6.1 | CVE-2024-9944 | 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. | woocommerce 6.7.0 | |
| 5.9 | CVE-2022-3590 | WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden. | wordpress 5.9.3 | |
| 5.4 | CVE-2023-2745 | WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter. This allows unauthenticated attackers to access and load arbitrary translation files. In cases where an attacker is able to upload a crafted translation file onto the site, such as via an upload form, this could be also used to perform a Cross-Site Scripting attack. | wordpress 5.9.3 | |
| 5.4 | CVE-2023-38000 | Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions. | wordpress 5.9.3 |
Vulnerability description
We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.
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.
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-1026 |
| OWASP Top 10 - 2017 | A9 - Using Components with Known Vulnerabilities |
| OWASP Top 10 - 2021 | A6 - Vulnerable and Outdated Components |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.thihongcucly.shop/ | PHPSESSID, ppwp_wp_session | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: PHPSESSID=8e79fp0mucr8f3m0ih6tjhck4t Set-Cookie: ppwp_wp_session=7f76c4a4dd0a22d9fe8d5e21c9a313b3%7C%7C1744498642%7C%7C1744498282 |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.thihongcucly.shop/ | PHPSESSID, ppwp_wp_session | Set-Cookie: PHPSESSID=8e79fp0mucr8f3m0ih6tjhck4t Set-Cookie: ppwp_wp_session=7f76c4a4dd0a22d9fe8d5e21c9a313b3%7C%7C1744498642%7C%7C1744498282 |
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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://www.thihongcucly.shop/ | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://www.thihongcucly.shop/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://www.thihongcucly.shop/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| URL | Evidence |
|---|---|
| https://www.thihongcucly.shop/ | 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-693 |
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| Software / Version | Category |
|---|---|
| Animate.css | UI frameworks |
| Contact Form 7 5.6.1 | WordPress plugins, Form builders |
| Font Awesome | Font scripts |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| core-js 3.19.1 | JavaScript libraries |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| prettyPhoto | JavaScript libraries |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| ProfilePress 4.0.3 | WordPress plugins |
| Select2 | JavaScript libraries |
| WooCommerce 6.7.0 | Ecommerce, WordPress plugins |
| WordPress 5.9.3 | CMS, Blogs |
| wpBakery | Page builders, WordPress plugins |
| Cloudflare | CDN |
| Lodash 1.13.1 | JavaScript libraries |
| Max Mega Menu 2.9.7 | Widgets, WordPress plugins |
| RSS | Miscellaneous |
| Slider Revolution 6.5.19 | Widgets, Photo galleries |
| Cart Functionality | Ecommerce |
| Yoast SEO 19.4 | SEO, WordPress plugins |
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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
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).
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
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.
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Risk level | CVSS | CVE | Summary |
|---|---|---|---|
| 8.8 | CVE-2023-52222 | Cross-Site Request Forgery (CSRF) vulnerability in Automattic WooCommerce.This issue affects WooCommerce: from n/a through 8.2.2. | |
| 6.1 | CVE-2024-9944 | 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. |
Vulnerability description
Vulnerabilities found for WooCommerce 6.7.0
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.;
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
| Risk level | CVSS | CVE | Summary |
|---|---|---|---|
| 8.8 | CVE-2023-52222 | Cross-Site Request Forgery (CSRF) vulnerability in Automattic WooCommerce.This issue affects WooCommerce: from n/a through 8.2.2. | |
| 6.1 | CVE-2024-9944 | 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. |
Vulnerability description
Vulnerabilities found for WooCommerce 6.7.0
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.;
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
| Risk level | CVSS | CVE | Summary |
|---|---|---|---|
| 8.8 | CVE-2023-52222 | Cross-Site Request Forgery (CSRF) vulnerability in Automattic WooCommerce.This issue affects WooCommerce: from n/a through 8.2.2. | |
| 6.1 | CVE-2024-9944 | 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. |
Vulnerability description
Vulnerabilities found for WooCommerce 6.7.0
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.;
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
| Risk level | CVSS | CVE | Summary |
|---|---|---|---|
| 6.1 | CVE-2022-43497 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | |
| 6.1 | CVE-2022-43500 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | |
| 5.9 | CVE-2022-3590 | WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden. | |
| 5.4 | CVE-2023-2745 | WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter. This allows unauthenticated attackers to access and load arbitrary translation files. In cases where an attacker is able to upload a crafted translation file onto the site, such as via an upload form, this could be also used to perform a Cross-Site Scripting attack. | |
| 5.4 | CVE-2023-38000 | Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions. |
Vulnerability description
Vulnerabilities found for WordPress 5.9.3
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.;
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
| Risk level | CVSS | CVE | Summary |
|---|---|---|---|
| 6.1 | CVE-2022-43497 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | |
| 6.1 | CVE-2022-43500 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | |
| 5.9 | CVE-2022-3590 | WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden. | |
| 5.4 | CVE-2023-2745 | WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter. This allows unauthenticated attackers to access and load arbitrary translation files. In cases where an attacker is able to upload a crafted translation file onto the site, such as via an upload form, this could be also used to perform a Cross-Site Scripting attack. | |
| 5.4 | CVE-2023-38000 | Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions. |
Vulnerability description
Vulnerabilities found for WordPress 5.9.3
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.;
Recommendation
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
| Risk level | CVSS | CVE | Summary |
|---|---|---|---|
| 6.1 | CVE-2022-43497 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | |
| 6.1 | CVE-2022-43500 | Cross-site scripting vulnerability in WordPress versions prior to 6.0.3 allows a remote unauthenticated attacker to inject an arbitrary script. The developer also provides new patched releases for all versions since 3.7. | |
| 5.9 | CVE-2022-3590 | WordPress is affected by an unauthenticated blind SSRF in the pingback feature. Because of a TOCTOU race condition between the validation checks and the HTTP request, attackers can reach internal hosts that are explicitly forbidden. | |
| 5.4 | CVE-2023-2745 | WordPress Core is vulnerable to Directory Traversal in versions up to, and including, 6.2, via the ‘wp_lang’ parameter. This allows unauthenticated attackers to access and load arbitrary translation files. In cases where an attacker is able to upload a crafted translation file onto the site, such as via an upload form, this could be also used to perform a Cross-Site Scripting attack. | |
| 5.4 | CVE-2023-38000 | Auth. Stored (contributor+) Cross-Site Scripting (XSS) vulnerability in WordPress core 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.1.3, from 6.0 through 6.0.5, from 5.9 through 5.9.7 and Gutenberg plugin <= 16.8.0 versions. |
Vulnerability description
Vulnerabilities found for WordPress 5.9.3
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.;
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 that WordPress has reached the End-of-Life (EOL).
Version detected: 5.9.3 End-of-life date: 2022-05-24 Latest version for the cycle: 5.9.10 This release cycle (5.9) doesn't have long-term-support (LTS). The cycle was released on 2022-01-25 and its latest release date was 2024-06-24.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
We managed to detect that WordPress has reached the End-of-Life (EOL).
Version detected: 5.9.3 End-of-life date: 2022-05-24 Latest version for the cycle: 5.9.10 This release cycle (5.9) doesn't have long-term-support (LTS). The cycle was released on 2022-01-25 and its latest release date was 2024-06-24.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| thihongcucly.shop | A | IPv4 address | 104.21.27.68 |
| thihongcucly.shop | A | IPv4 address | 172.67.169.8 |
| thihongcucly.shop | NS | Name server | archer.ns.cloudflare.com |
| thihongcucly.shop | NS | Name server | coco.ns.cloudflare.com |
| thihongcucly.shop | SOA | Start of Authority | archer.ns.cloudflare.com. dns.cloudflare.com. 2369867915 10000 2400 604800 1800 |
| thihongcucly.shop | AAAA | IPv6 address | 2606:4700:3036::6815:1b44 |
| thihongcucly.shop | AAAA | IPv6 address | 2606:4700:3037::ac43:a908 |
| thihongcucly.shop | TXT | Text record | "google-site-verification=BrnE-srtRVXdTpnYB6wgiqhsjIh6IGn4YlHYgnbt1ZQ" |
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
Vulnerability description
OS detection couldn't determine the operating system.
Evidence
| Software / Version | Category |
|---|---|
| WordPress 5.9.3 | CMS, Blogs |
| Slider Revolution 6.5.19 | Widgets, Photo galleries |
| MySQL | Databases |
| PHP | Programming languages |
| Contact Form 7 5.6.1 | WordPress plugins, Form builders |
| wpBakery | Page builders, WordPress plugins |
| WooCommerce 6.7.0 | Ecommerce, WordPress plugins |
| ProfilePress 4.0.3 | WordPress plugins |
| Yoast SEO 19.4 | SEO, WordPress plugins |
| Max Mega Menu 2.9.7 | Widgets, WordPress plugins |
| Select2 | JavaScript libraries |
| prettyPhoto | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Cloudflare | CDN |
| HTTP/3 | 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.
Evidence
| Software / Version | Category |
|---|---|
| WordPress 5.9.3 | CMS, Blogs |
| Slider Revolution 6.5.19 | Widgets, Photo galleries |
| MySQL | Databases |
| PHP | Programming languages |
| Contact Form 7 5.6.1 | WordPress plugins, Form builders |
| wpBakery | Page builders, WordPress plugins |
| WooCommerce 6.7.0 | Ecommerce, WordPress plugins |
| ProfilePress 4.0.3 | WordPress plugins |
| Yoast SEO 19.4 | SEO, WordPress plugins |
| Max Mega Menu 2.9.7 | Widgets, WordPress plugins |
| Select2 | JavaScript libraries |
| prettyPhoto | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Lodash 1.13.1 | JavaScript libraries |
| core-js 3.19.1 | JavaScript libraries |
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 |
|---|---|
| Cart Functionality | Ecommerce |
| WordPress 5.9.3 | CMS, Blogs |
| Slider Revolution 6.5.19 | Widgets, Photo galleries |
| MySQL | Databases |
| PHP | Programming languages |
| Animate.css | UI frameworks |
| Contact Form 7 5.6.1 | WordPress plugins, Form builders |
| GSAP | JavaScript frameworks |
| wpBakery | Page builders, WordPress plugins |
| WooCommerce 6.7.0 | Ecommerce, WordPress plugins |
| ProfilePress 4.0.3 | WordPress plugins |
| Yoast SEO 19.4 | SEO, WordPress plugins |
| Max Mega Menu 2.9.7 | Widgets, WordPress plugins |
| OWL Carousel | JavaScript libraries |
| Twitter Emoji (Twemoji) 13.1.0 | Font scripts |
| Select2 | JavaScript libraries |
| prettyPhoto | JavaScript libraries |
| jQuery Migrate 3.3.2 | JavaScript libraries |
| jQuery 3.6.0 | JavaScript libraries |
| core-js 3.19.1 | JavaScript libraries |
| Google Font API | Font scripts |
| Font Awesome | Font scripts |
| Cloudflare | CDN |
| RSS | Miscellaneous |
| Open Graph | Miscellaneous |
| HTTP/3 | Miscellaneous |
| Lodash 1.13.1 | JavaScript libraries |
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 |
|---|---|
| Cloudflare | CDN |
| HTTP/3 | 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.