Vulnerability Scan Result
| Title: | Willkommen bei easylohn - deinem payroll profi |
| Description: | Willkommen bei easylohn – dein Partner für einfache & sichere Lohnabrechnung. Wir übernehmen deine Payroll, damit du Zeit & Kosten sparst. |
| ip_address | 195.201.93.140 |
| country | DE  |
| network_name | Hetzner Online GmbH |
| asn | AS24940 |
21/tcp | ftp | ProFTPD - |
22/tcp | ssh | OpenSSH 9.6p1 Ubuntu 3ubuntu13.14 |
25/tcp | smtp | Postfix smtpd - |
53/tcp | domain | - - |
80/tcp | http | nginx - |
106/tcp | tcpwrapped | - - |
110/tcp | pop3 | Dovecot pop3d - |
143/tcp | imap | Dovecot imapd - |
443/tcp | https | nginx - |
465/tcp | smtp | Postfix smtpd - |
993/tcp | imap | Dovecot imapd - |
995/tcp | pop3 | Dovecot pop3d - |
8443/tcp | https | sw-cp-server - |
| Software / Version | Category |
|---|---|
| Borlabs Cookie | Cookie compliance, WordPress plugins |
| cdnjs | CDN |
| Clipboard.js | JavaScript libraries |
| Contact Form 7 | WordPress plugins, Form builders |
| Elementor 3.34.0 | Page builders, WordPress plugins |
| Font Awesome | Font scripts |
| jQuery Migrate | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| GSAP | JavaScript frameworks |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP 8.3.30 | Programming languages |
| Vue.js | JavaScript frameworks |
| Priority Hints | Performance |
| WordPress 6.9 | CMS, Blogs |
| WPMU DEV Smush | WordPress plugins |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| HSTS | Security |
| RSS | Miscellaneous |
| Yoast SEO 26.8 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Borlabs Cookie | Cookie compliance, WordPress plugins |
| cdnjs | CDN |
| Clipboard.js | JavaScript libraries |
| Contact Form 7 | WordPress plugins, Form builders |
| Elementor 3.34.0 | Page builders, WordPress plugins |
| Font Awesome | Font scripts |
| jQuery Migrate | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| GSAP | JavaScript frameworks |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP 8.3.30 | Programming languages |
| Vue.js | JavaScript frameworks |
| Priority Hints | Performance |
| WordPress 6.9 | CMS, Blogs |
| WPMU DEV Smush | WordPress plugins |
| Cloudflare | CDN |
| Google Tag Manager | Tag managers |
| Lodash 1.13.7 | JavaScript libraries |
| HSTS | Security |
| RSS | Miscellaneous |
| Yoast SEO 26.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://easylohn.de/ | 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 |
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
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://easylohn.de/ | 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 | Email Address: mail@easylohn.de |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
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.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://easylohn.de/wp-json/oembed/1.0/embed | GET | Query: format=xml url=https://easylohn.de/ 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 | Possible API endpoint found at |
Vulnerability description
We found API endpoints while crawling the given web application.
Risk description
These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.
Recommendation
Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2026-02-03 05:48 EET Nmap scan report for easylohn.de (195.201.93.140) Host is up (0.028s latency). rDNS record for 195.201.93.140: static.140.93.201.195.clients.your-server.de
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 Ubuntu 3ubuntu13.14 (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.39 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 Post Office Protocol (POP3) service. Starting Nmap ( https://nmap.org ) at 2026-02-03 05:48 EET Nmap scan report for easylohn.de (195.201.93.140) Host is up (0.023s latency). rDNS record for 195.201.93.140: static.140.93.201.195.clients.your-server.de
PORT STATE SERVICE VERSION 995/tcp open ssl/pop3 Dovecot pop3d |_pop3-capabilities: SASL(PLAIN LOGIN DIGEST-MD5 CRAM-MD5) APOP TOP AUTH-RESP-CODE CAPA USER PIPELINING UIDL RESP-CODES Service Info: Host: plesk
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 7.16 seconds
Vulnerability description
We found that the Post Office Protocol (POP3) service is publicly accessible and doesn’t include STARTTLS capability. Email clients use the Post Office Protocol (POP) to download emails for user accounts. Some POP servers are initially set up to operate over an unsecured protocol. When email clients download email content through this plaintext protocol, it can pose a substantial risk to the organization's network, especially depending on which user account is set to receive the emails.
Risk description
Exposing this service online can enable attackers to conduct man-in-the-middle attacks, thereby gaining access to sensitive user credentials and the contents of emails. Given that POP3 operates via a plaintext protocol, the entirety of the data exchanged between the client and server is left unencrypted. This critical information could then be leveraged in further attacks on the organization's network.
Recommendation
We recommend turning off POP3 access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the POP3 service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, activating STARTTLS capability (switching the connection to a secure communication) or utilizing Secure POP3 (POP3S) is recommended, as this protocol employs encryption.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.easylohn.de | TXT | Text record | "v=DMARC1;p=quarantine;pct=100;rua=mailto:versand@easylohn.net" |
Vulnerability description
We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.
Risk description
Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.
Recommendation
To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.
Evidence
We found insecure DNS cookie usage on the following nameservers: shades19.rzone.de, docks07.rzone.de
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.easylohn.de | TXT | Text record | "v=DMARC1;p=quarantine;pct=100;rua=mailto:versand@easylohn.net" |
Vulnerability description
We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.
Risk description
Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.
Recommendation
We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.
Evidence
We managed to detect a publicly accessible File Transfer Protocol (FTP) service. PORT STATE SERVICE VERSION 21/tcp open ftp ProFTPD
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
| Software / Version | Category |
|---|---|
| WordPress 6.9 | CMS, Blogs |
| MySQL | Databases |
| PHP 8.3.30 | Programming languages |
| Contact Form 7 | WordPress plugins, Form builders |
| Nginx | Web servers, Reverse proxies |
| Vue.js | JavaScript frameworks |
| GSAP | JavaScript frameworks |
| WPMU DEV Smush | WordPress plugins |
| Elementor 3.34.0 | Page builders, WordPress plugins |
| Yoast SEO 26.8 | SEO, WordPress plugins |
| Cloudflare | CDN |
| Swiper | JavaScript libraries |
| Borlabs Cookie | Cookie compliance, WordPress plugins |
| jQuery Migrate | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Font Awesome | Font scripts |
| cdnjs | CDN |
| HSTS | Security |
| Underscore.js | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
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 |
|---|---|
| Plesk | Hosting panels |
| Nginx | Web servers, Reverse proxies |
| RequireJS | JavaScript frameworks |
| Prototype | JavaScript frameworks |
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 |
|---|---|---|---|
| easylohn.de | A | IPv4 address | 195.201.93.140 |
| easylohn.de | NS | Name server | shades19.rzone.de |
| easylohn.de | NS | Name server | docks07.rzone.de |
| easylohn.de | MX | Mail server | 10 easylohn-de.mail.protection.outlook.com |
| easylohn.de | SOA | Start of Authority | shades19.rzone.de. hostmaster.strato-rz.de. 2022031065 86400 7200 604800 300 |
| easylohn.de | TXT | Text record | "MS=ms38663280" |
| easylohn.de | TXT | Text record | "google-site-verification=kX0gfv4ATvapT1IsanAWfDeGG8tRKrWjmPc3fJBDxa4" |
| easylohn.de | TXT | Text record | "seobility=864c1e80c0fcddf5e9f5560362188200" |
| easylohn.de | SPF | Sender Policy Framework | "v=spf1 ip4:78.47.53.40 ip4:195.201.93.140 include:spf.protection.outlook.com -all" |
| _dmarc.easylohn.de | TXT | Text record | "v=DMARC1;p=quarantine;pct=100;rua=mailto:versand@easylohn.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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| easylohn.de | SPF | Sender Policy Framework | "v=spf1 ip4:78.47.53.40 ip4:195.201.93.140 include:spf.protection.outlook.com -all" |
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 5.0 - 5.4 | 96% |
Vulnerability description
OS Detection
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| domk | rsa | 1296 | "v=DKIM1; t=s; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMxdtsTy8K7yEHt+7DB4XH70Rd6v7rp2qai7gM1meDzlrwDlMzUi0mQC+dMY+AzmCE1jLNXAr3JL6kT8vD7KQai8avwGQzmlU3d0Z7etqTj1ttJQZxUTPM18bM3wVqc6h3Dppqx7kY91Td50r9MXBbu+DkhL1+RCfcPQxEvEf74QIDAQAB" |
| selector1 | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr907pIbA8IV02pnw8z5pbF8bXsvndQzZyGQZcmWTs+I384ODPaSIvBc7N5OB/q7oIArBGWHWL1SpSbLmRf3OpUmZTNk2Abx515C7IJr7gHT+rnAAZwlOsV82oX62BVuDZSeFgNMy23njw6pzpaZlnAFoOP2xJdjMdezUqx4uLC+o4aszpV+s8O03npLgC6Ll/" "jir4vwBc7wZGsQz0xaKBH/DAz0jkRlm5lotxd3dIRt100jCS4VFzuIitQe8zgiZBrsFfYjNh790PIEGDHbpj6gzBff5bBG6IREnBsgFkuKUlj4iFBLwqWSe3sTa4wSXCiza72PDd+epPtZ23TEy1QIDAQAB;" |