Vulnerability Scan Result
| Title: | Erasmusgram - Erasmus'tan daha fazlası |
| Description: | Erasmus'tan daha fazlası |
| ip_address | 176.53.74.108 |
| country | TR  |
| network_name | Radore VERI Merkezi Hizmetleri A.S |
| asn | AS42926 |
21/tcp | ftp | Pure-FTPd - |
22/tcp | ssh | OpenSSH 8.9p1 Ubuntu 3ubuntu0.11 |
25/tcp | smtp | Postfix smtpd - |
53/tcp | domain | PowerDNS Authoritative Server 4.5.3 |
80/tcp | http | LiteSpeed - |
110/tcp | pop3 | Dovecot pop3d - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | LiteSpeed - |
465/tcp | smtp | Postfix smtpd - |
587/tcp | smtp | Postfix smtpd - |
993/tcp | imaps | - - |
995/tcp | pop3s | - - |
| Software / Version | Category |
|---|---|
| All in One SEO Pack 4.8.4.1 | SEO, WordPress plugins |
| Clipboard.js | JavaScript libraries |
| Funding Choices | Cookie compliance |
| Font Awesome | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| Gravatar | Miscellaneous |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| LiteSpeed | Web servers |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Redis | Databases |
| Twitter Emoji (Twemoji) | Font scripts |
| Underscore.js | JavaScript libraries |
| WordPress 6.8.1 | CMS, Blogs |
| Redis Object Cache | Caching |
| AMP | JavaScript frameworks |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| MonsterInsights | WordPress plugins, Analytics |
| RSS | Miscellaneous |
| W3 Total Cache | Caching, WordPress plugins |
Web Application Vulnerabilities
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.erasmusgram.com/ | 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 |
|
| https://www.erasmusgram.com/ | GET | Query: s=search 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 |
|
| https://www.erasmusgram.com/page/854 | 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
| URL | Evidence |
|---|---|
| https://www.erasmusgram.com/ | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.erasmusgram.com/ | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.erasmusgram.com/ | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.erasmusgram.com/ | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| All in One SEO Pack 4.8.4.1 | SEO, WordPress plugins |
| Clipboard.js | JavaScript libraries |
| Funding Choices | Cookie compliance |
| Font Awesome | Font scripts |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics | Analytics |
| Google Font API | Font scripts |
| Gravatar | Miscellaneous |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| LiteSpeed | Web servers |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| PHP | Programming languages |
| Redis | Databases |
| Twitter Emoji (Twemoji) | Font scripts |
| Underscore.js | JavaScript libraries |
| WordPress 6.8.1 | CMS, Blogs |
| Redis Object Cache | Caching |
| AMP | JavaScript frameworks |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| MonsterInsights | WordPress plugins, Analytics |
| RSS | Miscellaneous |
| W3 Total Cache | Caching, 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
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
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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-06-30 23:13 EEST Nmap scan report for www.erasmusgram.com (176.53.74.108) Host is up (0.055s latency). rDNS record for 176.53.74.108: server.erasmusgram.com
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 8.9p1 Ubuntu 3ubuntu0.11 (Ubuntu Linux; protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 1.72 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.erasmusgram.com | SPF | Sender Policy Framework | "v=spf1 a mx ip4:176.53.74.108 ~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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.erasmusgram.com | A | IPv4 address | 176.53.74.108 |
| www.erasmusgram.com | NS | Name server | ns1.erasmusgram.com |
| www.erasmusgram.com | NS | Name server | ns2.erasmusgram.com |
| www.erasmusgram.com | MX | Mail server | 10 erasmusgram.com |
| www.erasmusgram.com | SOA | Start of Authority | ns1.erasmusgram.com. hostmaster.erasmusgram.com. 1 10800 3600 1209600 3600 |
| www.erasmusgram.com | SPF | Sender Policy Framework | "v=spf1 a mx ip4:176.53.74.108 ~all" |
| www.erasmusgram.com | CNAME | Canonical name | erasmusgram.com |
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.0 | 92% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress 6.8.1 | CMS, Blogs |
| Redis | Databases |
| MySQL | Databases |
| PHP | Programming languages |
| Redis Object Cache | Caching |
| LiteSpeed | Web servers |
| AMP | JavaScript frameworks |
| W3 Total Cache | Caching, WordPress plugins |
| All in One SEO Pack 4.8.4.1 | SEO, WordPress plugins |
| MonsterInsights | WordPress plugins, Analytics |
| Underscore.js | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| jQuery Migrate | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Google AdSense | Advertising |
| Funding Choices | Cookie compliance |
| HTTP/3 | Miscellaneous |
| Google Font API | Font scripts |
| Font Awesome | Font scripts |
| Gravatar | Miscellaneous |
| 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
| Software / Version | Category |
|---|---|
| WordPress 6.8.1 | CMS, Blogs |
| Redis | Databases |
| MySQL | Databases |
| PHP | Programming languages |
| Redis Object Cache | Caching |
| LiteSpeed | Web servers |
| AMP | JavaScript frameworks |
| W3 Total Cache | Caching, WordPress plugins |
| All in One SEO Pack 4.8.4.1 | SEO, WordPress plugins |
| MonsterInsights | WordPress plugins, Analytics |
| Underscore.js | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| jQuery Migrate | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Google AdSense | Advertising |
| Funding Choices | Cookie compliance |
| HTTP/3 | Miscellaneous |
| Clipboard.js | JavaScript libraries |
| Gravatar | 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.