Vulnerability Scan Result
| Title: | صفحه اصلی - علّامه حسن زاده آملی |
| Description: | سایت نشر و حفظ آثار منقول و مکتوب حضرت علامه حسن زاده آملی رضوان الله تعالی علیه |
| ip_address | 94.182.142.42 |
| country | IR  |
| network_name | Aria Shatel Company Ltd |
| asn | AS31549 |
21/tcp | ftp | Pure-FTPd - |
25/tcp | smtp | - - |
53/tcp | domain | PowerDNS Authoritative Server 4.9.5 |
80/tcp | http | - - |
110/tcp | pop3 | Dovecot pop3d - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | - - |
587/tcp | smtp | Exim smtpd 4.98.2 |
993/tcp | imaps | - - |
995/tcp | pop3s | - - |
2087/tcp | eli | - - |
| Software / Version | Category |
|---|---|
| jQuery Migrate | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| Lightbox | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Priority Hints | Performance |
| WordPress 6.6.2 | CMS, Blogs |
| reCAPTCHA | Security |
| HSTS | Security |
| RSS | Miscellaneous |
| Yoast SEO 22.8 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://najmeddinamoli.ir/ | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 |
|
Vulnerability description
We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Risk description
The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.
Recommendation
Ensure that all external resources the page references are loaded using HTTPS.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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
| Software / Version | Category |
|---|---|
| jQuery Migrate | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| jQuery | JavaScript libraries |
| Lightbox | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Priority Hints | Performance |
| WordPress 6.6.2 | CMS, Blogs |
| reCAPTCHA | Security |
| HSTS | Security |
| RSS | Miscellaneous |
| Yoast SEO 22.8 | 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.
Evidence
| URL | Evidence |
|---|---|
| https://najmeddinamoli.ir/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-693 |
| 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.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp Pure-FTPd
Vulnerability description
We found that the File Transfer Protocol (FTP) service is publicly accessible. The FTP enables client systems to connect to upload and download files. Nonetheless, FTP lacks encryption for the data exchanged between the server and the client, leaving all transferred data exposed in plaintext.
Risk description
Exposing this service online can enable attackers to execute man-in-the-middle attacks, capturing sensitive user credentials and the contents of files because FTP operates without encryption. The entirety of the communication between the client and the server remains unsecured in plaintext. This acquired information could further facilitate additional attacks within the network.
Recommendation
We recommend turning off FTP access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the FTP service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, utilizing SFTP (Secure File Transfer Protocol) is recommended as this protocol employs encryption to secure data transfers.
Evidence
We didn't find any TXT records associated with the target.
Vulnerability description
We found that the target server has no DMARC policy configured. A missing DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy means that the domain is not enforcing any DMARC policies to protect against email spoofing and phishing attacks. Without DMARC, even if SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) are configured, there is no mechanism to tell receiving email servers how to handle messages that fail authentication. This leaves the domain vulnerable to abuse, such as email spoofing and impersonation.
Risk description
Without a DMARC policy, your domain is highly vulnerable to email spoofing, allowing attackers to impersonate your brand and send fraudulent emails that appear legitimate. This can lead to phishing attacks targeting your customers, employees, or partners, potentially resulting in stolen credentials, financial loss, or unauthorized access to sensitive systems. Additionally, repeated spoofing attempts can severely damage your brand's reputation, as recipients may lose trust in communications from your domain, associating your brand with malicious activity. The absence of DMARC also prevents you from monitoring and mitigating email-based attacks, leaving your domain exposed to ongoing abuse.
Recommendation
We recommend implementing a DMARC policy for your domain. Start by configuring a DMARC record with a policy of p=none, which will allow you to monitor email flows without impacting legitimate emails. This initial setup helps identify how emails from your domain are being processed by recipient servers. Once you’ve verified that legitimate emails are passing SPF and DKIM checks, you can gradually enforce stricter policies like p=quarantine or p=reject to protect against spoofing and phishing attacks. Additionally, include rua and ruf email addresses in the DMARC record to receive aggregate and forensic reports. These reports will provide valuable insights into authentication failures and help you detect any spoofing attempts.
Evidence
We found insecure EDNS configuration on the following nameservers: ns2.webhosthub.net, ns1.webhosthub.net ns2.webhosthub.net:
ns1.webhosthub.net:
Vulnerability description
We found that the server does not properly implement EDNS (Extension Mechanisms for DNS). EDNS allows larger DNS packets and supports modern features such as DNSSEC.
Risk description
The risk exists because improper or missing EDNS support can lead to truncated responses, degraded DNS performance, and compatibility issues with DNSSEC. This exposes users to risks such as incomplete DNS resolution and failed DNSSEC validation.
Recommendation
We recommend ensuring the proper implementation of EDNS on the DNS server. Update the DNS server software to support EDNS fully, including modern features like DNSSEC. Regularly test DNS configurations to ensure compliance and performance.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| najmeddinamoli.ir | SPF | Sender Policy Framework | "v=spf1 ip4:94.182.142.42 +a +mx +ip4:185.73.3.7 +ip4:95.217.47.172 +ip4:188.40.210.105 +ip4:176.9.200.50 +ip4:208.74.123.2 +ip4:185.187.51.8 +ip4:172.16.10.58 +ip4:69.90.250.78 +ip4:172.16.1.58 ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns2.webhosthub.net, ns1.webhosthub.net
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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAycymA1rhfJNdR/vv34/YKBzpmb0+L+Sw/WkFVPxTqMIHPpPMd/IEptwPfsG1+X0HHI8HBo6dmTLNlTfeTH9OEm8xBc51gdbNoohRRzMdfKf3R5tF4FeETTvU3RBjlp9+7qS9HrUJ9IMkMk9fRNsoBL+QOvfRuubwALBPsB9geerk9l8SSQg+q9DYWCwChr5/g" "cLfoOkTgpRHf+VN6x3935fAoiEtDeu9lhVqG4nK0CRt1rnkB4WPjowKnBiiX8l+kqmhUqkedf0XJkvOeiYRSH/tNhGAJBkfVTW1Towvfp0V5dOUOEYDD288Dzg0NgwZl/KUgxdHHEhU84vamn7hWQIDAQAB;" |
Vulnerability description
We found that the DKIM record uses common selectors. The use of common DKIM selectors such as default, test, dkim, or mail may indicate a lack of proper customization or key management. Attackers often target domains using such selectors because they suggest that the domain is relying on default configurations, which could be less secure and easier to exploit. This can increase the risk of DKIM key exposure or misuse.
Risk description
Using a common DKIM selector makes it easier for attackers to predict and exploit email authentication weaknesses. Attackers may attempt to find corresponding DKIM keys or improperly managed records associated with common selectors. If a common selector is coupled with a weak key length or poor key management practices, it significantly increases the likelihood of email spoofing and phishing attacks.
Recommendation
We recommend using unique, customized selectors for each DKIM key to make it more difficult for attackers to predict and target the domain's DKIM records. Regularly rotate selectors and associated keys to further strengthen the security of your domain's email authentication infrastructure.
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.6.2 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Yoast SEO 22.8 | SEO, WordPress plugins |
| Lightbox | JavaScript libraries |
| jQuery Migrate | JavaScript libraries |
| jQuery | JavaScript libraries |
| HSTS | Security |
| HTTP/3 | Miscellaneous |
| reCAPTCHA | Security |
| Priority Hints | Performance |
| 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.
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| default | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAycymA1rhfJNdR/vv34/YKBzpmb0+L+Sw/WkFVPxTqMIHPpPMd/IEptwPfsG1+X0HHI8HBo6dmTLNlTfeTH9OEm8xBc51gdbNoohRRzMdfKf3R5tF4FeETTvU3RBjlp9+7qS9HrUJ9IMkMk9fRNsoBL+QOvfRuubwALBPsB9geerk9l8SSQg+q9DYWCwChr5/g" "cLfoOkTgpRHf+VN6x3935fAoiEtDeu9lhVqG4nK0CRt1rnkB4WPjowKnBiiX8l+kqmhUqkedf0XJkvOeiYRSH/tNhGAJBkfVTW1Towvfp0V5dOUOEYDD288Dzg0NgwZl/KUgxdHHEhU84vamn7hWQIDAQAB;" |
Evidence
| Operating System | Accuracy |
|---|---|
| Fortinet FortiGate 100D firewall | 87% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| najmeddinamoli.ir | A | IPv4 address | 94.182.142.42 |
| najmeddinamoli.ir | NS | Name server | ns2.webhosthub.net |
| najmeddinamoli.ir | NS | Name server | ns1.webhosthub.net |
| najmeddinamoli.ir | MX | Mail server | 0 najmeddinamoli.ir |
| najmeddinamoli.ir | SOA | Start of Authority | ns1.webhosthub.net. arpihm_2004.yahoo.com. 2025071806 3600 1800 1209600 86400 |
| najmeddinamoli.ir | SPF | Sender Policy Framework | "v=spf1 ip4:94.182.142.42 +a +mx +ip4:185.73.3.7 +ip4:95.217.47.172 +ip4:188.40.210.105 +ip4:176.9.200.50 +ip4:208.74.123.2 +ip4:185.187.51.8 +ip4:172.16.10.58 +ip4:69.90.250.78 +ip4:172.16.1.58 ~all" |
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.