Vulnerability Scan Result

| Title: | Access Denied |
| Description: | No description found |
| ip_address | 173.222.106.17 |
| country | IT |
| network_name | Akamai International B.V. |
| asn | AS20940 |
| ip_address | 173.222.106.19 |
| country | IT |
| network_name | Akamai International B.V. |
| asn | AS20940 |
80/tcp | http | AkamaiGHost - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Akamai | CDN |
| Astro 5.17.1 | Static site generator, JavaScript frameworks |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Funding Choices | Cookie compliance |
| Google Font API | Font scripts |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| WordPress | CMS, Blogs |
| Akamai Bot Manager | Security |
| GoDaddy Domain Parking | Domain parking |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-41067 | 6.1 | 0.00189 | 0.08655 | Astro is a web framework. Prior to 6.1.6, the defineScriptVars function in Astro's server-side rendering pipeline uses a case-sensitive regex /<\/script>/g to sanitize values injected into inline <script> tags via the define:vars directive. HTML parsers close <script> elements case-insensitively and also accept whitespace or / before the closing >, allowing an attacker to bypass the sanitization with payloads like </Script>, </script >, or </script/> and inject arbitrary HTML/JavaScript. This vulnerability is fixed in 6.1.6. |
| CVE-2026-45028 | 2.9 | 0.00144 | 0.0397 | Astro is a web framework. Astro versions prior to 6.1.10 used AES-GCM encryption to protect the confidentiality and integrity of server island props and slots parameters, but did not bind the ciphertext to its intended component or parameter type. An attacker could replay one component's encrypted props (p) value as another component's slots (s) value, or vice versa. Since slots contain raw unescaped HTML while props may contain user-controlled values, this could lead to XSS in applications. This occurs when the application uses server islands, two different server island components share the same key name for a prop and a slot, and an attacker has full control over the value of the overlapping prop (requires a dynamically rendered page). This vulnerability is fixed in 6.1.10. |
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
| Software / Version | Category |
|---|---|
| Akamai | CDN |
| Astro 5.17.1 | Static site generator, JavaScript frameworks |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Funding Choices | Cookie compliance |
| Google Font API | Font scripts |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| WordPress | CMS, Blogs |
| Akamai Bot Manager | Security |
| GoDaddy Domain Parking | Domain parking |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
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 |
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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| GoDaddy Domain Parking | Domain parking |
| Astro 5.17.1 | Static site generator, JavaScript frameworks |
| Amazon Web Services | PaaS |
| Akamai | CDN |
| Google AdSense | Advertising |
| Funding Choices | Cookie compliance |
| Akamai Bot Manager | Security |
| Amazon S3 | CDN |
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 |
| MySQL | Databases |
| PHP | Programming languages |
| GoDaddy Domain Parking | Domain parking |
| Astro 5.17.1 | Static site generator, JavaScript frameworks |
| Amazon Web Services | PaaS |
| Akamai | CDN |
| Google AdSense | Advertising |
| Funding Choices | Cookie compliance |
| Akamai Bot Manager | Security |
| Amazon S3 | CDN |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.dot-news.org | A | IPv4 address | 173.222.106.189 |
| www.dot-news.org | A | IPv4 address | 173.222.106.152 |
| www.dot-news.org | AAAA | IPv6 address | 2a02:26f0:8d00:14::213:7c8d |
| www.dot-news.org | AAAA | IPv6 address | 2a02:26f0:8d00:14::213:7c87 |
| www.dot-news.org | CNAME | Canonical name | searchhounds.com.edgekey.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 |
|---|---|
| Linux 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection
