Vulnerability Scan Result
| Title: | Beautiful - Doxa Dollar |
| Description: | No description found |
| IP address | 212.71.124.186 |
| 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 |
| IP address | 212.71.124.189 |
| Country | CH |
| AS number | AS24951 |
| Net name | Everyware Ag |
| IP address | 193.118.59.140 |
| Country | GB  |
| AS number | AS21859 |
| Net name | Zenlayer Inc |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| All in One SEO Pack 4.4.0.1 | SEO, WordPress plugins |
| Contact Form 7 5.7.7 | WordPress plugins, Form builders |
| Magnific Popup 6.3.1 | JavaScript libraries |
| Elementor 3.14.1 | Page builders, WordPress plugins |
| ZURB Foundation | UI frameworks |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Breadcrumb NavXT 7.2.0 | WordPress plugins |
| GiveWP 2.9.5 | Fundraising & donations, WordPress plugins |
| Google Font API | Font scripts |
| Gravatar | Miscellaneous |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Underscore.js 1.13.4 | JavaScript libraries |
| Priority Hints | Performance |
| WordPress 6.3.1 | CMS, Blogs |
| WPForms 1.8.2.1 | WordPress plugins, Form builders |
| HSTS | Security |
| RSS | Miscellaneous |
| Slider Revolution 6.6.14 | Widgets, Photo galleries |
Web Application Vulnerabilities
Evidence
| Risk Level | CVSS | CVE | Summary | Affected software |
|---|---|---|---|---|
| 10 | CVE-2024-37099 | Deserialization of Untrusted Data vulnerability in Liquid Web GiveWP allows Object Injection.This issue affects GiveWP: from n/a through 3.14.1. | givewp 2.9.5 | |
| 9.8 | CVE-2023-22719 | Improper Neutralization of Formula Elements in a CSV File vulnerability in GiveWP.This issue affects GiveWP: from n/a through 2.25.1. | givewp 2.9.5 | |
| 9.8 | CVE-2023-32513 | Deserialization of Untrusted Data vulnerability in GiveWP GiveWP – Donation Plugin and Fundraising Platform.This issue affects GiveWP – Donation Plugin and Fundraising Platform: from n/a through 2.25.3. | givewp 2.9.5 | |
| 9.8 | CVE-2023-0224 | The GiveWP WordPress plugin before 2.24.1 does not properly escape user input before it reaches SQL queries, which could let unauthenticated attackers perform SQL Injection attacks | givewp 2.9.5 | |
| 9.8 | CVE-2024-5932 | The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files. | givewp 2.9.5 | |
| 6.1 | CVE-2023-7063 | The WPForms Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via form submission parameters in all versions up to, and including, 1.8.5.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. | wpforms 1.8.2.1 | |
| 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.3.1 | |
| 5.3 | CVE-2023-5561 | WordPress does not properly restrict which user fields are searchable via the REST API, allowing unauthenticated attackers to discern the email addresses of users who have published public posts on an affected website via an Oracle style attack | wordpress 6.3.1 | |
| 4.3 | CVE-2023-39999 | Exposure of Sensitive Information to an Unauthorized Actor in WordPress from 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.13, from 6.0 through 6.0.5, from 5.9 through 5.9.7, from 5.8 through 5.8.7, from 5.7 through 5.7.9, from 5.6 through 5.6.11, from 5.5 through 5.5.12, from 5.4 through 5.4.13, from 5.3 through 5.3.15, from 5.2 through 5.2.18, from 5.1 through 5.1.16, from 5.0 through 5.0.19, from 4.9 through 4.9.23, from 4.8 through 4.8.22, from 4.7 through 4.7.26, from 4.6 through 4.6.26, from 4.5 through 4.5.29, from 4.4 through 4.4.30, from 4.3 through 4.3.31, from 4.2 through 4.2.35, from 4.1 through 4.1.38. | wordpress 6.3.1 |
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://ekiye-pyaaa-aaaad-qfuda-cai.icp0.io/index.php/tag/beautiful/index.html | 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://ekiye-pyaaa-aaaad-qfuda-cai.icp0.io/index.php/tag/beautiful/index.html | 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://ekiye-pyaaa-aaaad-qfuda-cai.icp0.io/index.php/tag/beautiful/index.html | 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 |
|---|---|
| All in One SEO Pack 4.4.0.1 | SEO, WordPress plugins |
| Contact Form 7 5.7.7 | WordPress plugins, Form builders |
| Magnific Popup 6.3.1 | JavaScript libraries |
| Elementor 3.14.1 | Page builders, WordPress plugins |
| ZURB Foundation | UI frameworks |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Breadcrumb NavXT 7.2.0 | WordPress plugins |
| GiveWP 2.9.5 | Fundraising & donations, WordPress plugins |
| Google Font API | Font scripts |
| Gravatar | Miscellaneous |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Underscore.js 1.13.4 | JavaScript libraries |
| Priority Hints | Performance |
| WordPress 6.3.1 | CMS, Blogs |
| WPForms 1.8.2.1 | WordPress plugins, Form builders |
| HSTS | Security |
| RSS | Miscellaneous |
| Slider Revolution 6.6.14 | Widgets, Photo galleries |
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 |
|---|---|---|---|
| 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. | |
| 5.3 | CVE-2023-5561 | WordPress does not properly restrict which user fields are searchable via the REST API, allowing unauthenticated attackers to discern the email addresses of users who have published public posts on an affected website via an Oracle style attack | |
| 4.3 | CVE-2023-39999 | Exposure of Sensitive Information to an Unauthorized Actor in WordPress from 6.3 through 6.3.1, from 6.2 through 6.2.2, from 6.1 through 6.13, from 6.0 through 6.0.5, from 5.9 through 5.9.7, from 5.8 through 5.8.7, from 5.7 through 5.7.9, from 5.6 through 5.6.11, from 5.5 through 5.5.12, from 5.4 through 5.4.13, from 5.3 through 5.3.15, from 5.2 through 5.2.18, from 5.1 through 5.1.16, from 5.0 through 5.0.19, from 4.9 through 4.9.23, from 4.8 through 4.8.22, from 4.7 through 4.7.26, from 4.6 through 4.6.26, from 4.5 through 4.5.29, from 4.4 through 4.4.30, from 4.3 through 4.3.31, from 4.2 through 4.2.35, from 4.1 through 4.1.38. |
Vulnerability description
Vulnerabilities found for WordPress 6.3.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.;
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-2023-7063 | The WPForms Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via form submission parameters in all versions up to, and including, 1.8.5.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
Vulnerability description
Vulnerabilities found for WPForms 1.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.;
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 |
|---|---|---|---|
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | A | IPv4 address | 193.118.59.140 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | A | IPv4 address | 212.71.124.189 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | A | IPv4 address | 212.71.124.188 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | A | IPv4 address | 212.71.124.186 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | A | IPv4 address | 212.71.124.187 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | NS | Name server | hassan.ns.cloudflare.com |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | NS | Name server | lara.ns.cloudflare.com |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | SOA | Start of Authority | hassan.ns.cloudflare.com. dns.cloudflare.com. 2370275289 10000 2400 604800 1800 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:61ff:fe45:43ab |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:5aff:fef2:9428 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | AAAA | IPv6 address | 2a0b:21c0:4003:2:5000:55ff:feb8:5f89 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:45ff:feb5:f777 |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | AAAA | IPv6 address | 2a00:fb01:400:200:5000:eeff:fe3d:aa0d |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | SPF | Sender Policy Framework | "v=spf1 -all" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "comodoca.com" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "digicert.com; cansignhttpexchanges=yes" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "pki.goog; cansignhttpexchanges=yes" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issue "ssl.com" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "comodoca.com" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "digicert.com; cansignhttpexchanges=yes" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "letsencrypt.org" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "pki.goog; cansignhttpexchanges=yes" |
| ekiye-pyaaa-aaaad-qfuda-cai.icp0.io | CAA | Certificate Authority Authorization | 0 issuewild "ssl.com" |
| ekiye-pyaaa-aaaad-qfuda-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.3.1 | CMS, Blogs |
| Slider Revolution 6.6.14 | Widgets, Photo galleries |
| MySQL | Databases |
| PHP | Programming languages |
| ZURB Foundation | UI frameworks |
| WPForms 1.8.2.1 | WordPress plugins, Form builders |
| Contact Form 7 5.7.7 | WordPress plugins, Form builders |
| Elementor 3.14.1 | Page builders, WordPress plugins |
| All in One SEO Pack 4.4.0.1 | SEO, WordPress plugins |
| GiveWP 2.9.5 | Fundraising & donations, WordPress plugins |
| Underscore.js 1.13.4 | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| Magnific Popup 6.3.1 | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| HSTS | Security |
| Priority Hints | Performance |
| 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.