Vulnerability Scan Result

IP address | 193.118.59.140 |
Country | GB ![]() |
AS number | AS21859 |
Net name | Zenlayer Inc |
IP address | 212.71.124.186 |
Country | CH ![]() |
AS number | AS24951 |
Net name | Everyware Ag |
IP address | 212.71.124.189 |
Country | CH ![]() |
AS number | AS24951 |
Net name | Everyware Ag |
IP address | 212.71.124.187 |
Country | CH ![]() |
AS number | AS24951 |
Net name | Everyware Ag |
IP address | 212.71.124.188 |
Country | CH ![]() |
AS number | AS24951 |
Net name | Everyware Ag |
80/tcp | http | - - |
443/tcp | https | - - |
Software / Version | Category |
---|---|
Elementor 3.7.6 | Page builders, WordPress plugins |
Font Awesome | Font scripts |
web-vitals | JavaScript libraries, RUM |
jQuery Migrate 3.3.2 | JavaScript libraries |
core-js 3.24.1 | JavaScript libraries |
Google Font API | Font scripts |
jQuery 3.6.0 | JavaScript libraries |
jQuery UI 1.13.1 | JavaScript libraries |
MySQL | Databases |
Open Graph | Miscellaneous |
PHP | Programming languages |
WordPress 6.0.2 | CMS, Blogs |
Astra | WordPress themes |
Cloudflare Browser Insights | Analytics, RUM |
HSTS | Security |
RSS | Miscellaneous |
Yoast SEO 19.6.1 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
Risk Level | CVSS | CVE | Summary | Affected software |
---|---|---|---|---|
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 6.0.2 | |
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 6.0.2 | |
6.1 | CVE-2022-31160 | jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`. | jquery_ui 1.13.1 | |
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 6.0.2 | |
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 6.0.2 | |
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 6.0.2 |
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 | Evidence |
---|---|
https://ltmfp-biaaa-aaaad-qd43a-cai.icp0.io/ | 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://ltmfp-biaaa-aaaad-qd43a-cai.icp0.io/ | 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
URL | Evidence |
---|---|
https://ltmfp-biaaa-aaaad-qd43a-cai.icp0.io/ | 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
Software / Version | Category |
---|---|
Elementor 3.7.6 | Page builders, WordPress plugins |
Font Awesome | Font scripts |
web-vitals | JavaScript libraries, RUM |
jQuery Migrate 3.3.2 | JavaScript libraries |
core-js 3.24.1 | JavaScript libraries |
Google Font API | Font scripts |
jQuery 3.6.0 | JavaScript libraries |
jQuery UI 1.13.1 | JavaScript libraries |
MySQL | Databases |
Open Graph | Miscellaneous |
PHP | Programming languages |
WordPress 6.0.2 | CMS, Blogs |
Astra | WordPress themes |
Cloudflare Browser Insights | Analytics, RUM |
HSTS | Security |
RSS | Miscellaneous |
Yoast SEO 19.6.1 | 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
Website is accessible.
Infrastructure 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 6.0.2
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
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | A | IPv4 address | 212.71.124.186 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | A | IPv4 address | 212.71.124.189 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | A | IPv4 address | 212.71.124.187 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | A | IPv4 address | 212.71.124.188 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | A | IPv4 address | 193.118.59.140 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | NS | Name server | hassan.ns.cloudflare.com |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | NS | Name server | lara.ns.cloudflare.com |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | SOA | Start of Authority | hassan.ns.cloudflare.com. dns.cloudflare.com. 2370275289 10000 2400 604800 1800 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:45ff:feb5:f777 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | AAAA | IPv6 address | 2a0b:21c0:4003:2:5000:55ff:feb8:5f89 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:eeff:fe3d:aa0d |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:61ff:fe45:43ab |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:5aff:fef2:9428 |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | SPF | Sender Policy Framework | "v=spf1 -all" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
ltmfp-biaaa-aaaad-qd43a-cai.icp0.io | CNAME | Canonical name | boundary.dfinity.network |
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
We managed to detect the redirect using the following Request / Response chain.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.
Evidence
Software / Version | Category |
---|---|
WordPress 6.0.2 | CMS, Blogs |
MySQL | Databases |
PHP | Programming languages |
Astra | WordPress themes |
Elementor 3.7.6 | Page builders, WordPress plugins |
Yoast SEO 19.6.1 | SEO, WordPress plugins |
jQuery Migrate | JavaScript libraries |
jQuery | JavaScript libraries |
Font Awesome | Font scripts |
Cloudflare Browser Insights | Analytics, RUM |
web-vitals | JavaScript libraries, RUM |
HSTS | Security |
Google Font API | Font scripts |
RSS | Miscellaneous |
Open Graph | 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.