Vulnerability Scan Result
| Title: | Landingi: AI Landing Page Operation System for Digital Marketers |
| Description: | Scale lead generation faster with AI-powered landing pages, enterprise-grade infrastructure, and proven marketing expertise. |
| ip_address | 162.159.135.42 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | Cloudflare http proxy - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | https | Cloudflare http proxy - |
| Software / Version | Category |
|---|---|
| HTTP/3 | Miscellaneous |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| HTTP/3 | Miscellaneous |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2024-6386 | 9.9 | 0.73911 | 0.98827 | No | The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6.12 via Twig Server-Side Template Injection. This is due to missing input validation and sanitization on the render function. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server. |
| CVE-2025-3488 | 6.4 | 0.00209 | 0.43405 | No | The WPML plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpml_language_switcher shortcode in versions 3.6.0 - 4.7.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. |
Vulnerability description
Vulnerabilities found for WPML 4.6.9
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.; 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
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 |
|---|---|---|---|
| _dmarc.landingi.com | TXT | Text record | "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@landingi.com; sp=quarantine; aspf=r;" |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.landingi.com | TXT | Text record | "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@landingi.com; sp=quarantine; aspf=r;" |
Vulnerability description
We found that the target uses p=quarantine in the DMARC policy. When a DMARC policy is set to p=quarantine, emails that fail DMARC validation are delivered but placed in the recipient’s spam or junk folder. Although it offers some protection, this policy is less strict than p=reject, which blocks such emails entirely.
Risk description
While emails failing DMARC validation are sent to the spam folder, users may still retrieve them from there, leading to a higher risk of phishing and spoofing attacks succeeding. Moreover, less strict enforcement may allow more fraudulent emails to reach user inboxes if misclassified.
Recommendation
We recommend considering moving to a stricter policy, such as p=reject, where emails that fail DMARC validation are completely rejected rather than delivered to spam folders. This reduces the risk of users interacting with potentially malicious emails.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-1008.awsdns-62.net, ns-1154.awsdns-16.org, ns-1554.awsdns-02.co.uk, ns-285.awsdns-35.com
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 |
|---|---|---|---|
| landingi.com | A | IPv4 address | 162.159.135.42 |
| landingi.com | NS | Name server | ns-1008.awsdns-62.net |
| landingi.com | NS | Name server | ns-1154.awsdns-16.org |
| landingi.com | NS | Name server | ns-1554.awsdns-02.co.uk |
| landingi.com | NS | Name server | ns-285.awsdns-35.com |
| landingi.com | MX | Mail server | 1 aspmx.l.google.com |
| landingi.com | MX | Mail server | 10 aspmx2.googlemail.com |
| landingi.com | MX | Mail server | 10 aspmx3.googlemail.com |
| landingi.com | MX | Mail server | 5 alt1.aspmx.l.google.com |
| landingi.com | MX | Mail server | 5 alt2.aspmx.l.google.com |
| landingi.com | SOA | Start of Authority | ns-1008.awsdns-62.net. awsdns-hostmaster.amazon.com. 2023061901 7200 900 1209600 86400 |
| landingi.com | TXT | Text record | "419f9dc49be6ce272e9c51c81d20516e708d343eb7724eed543816b8488c291" |
| landingi.com | TXT | Text record | "5dc2590a68e4c58f631ef667ba8a048c00e2c17d74eb917716d5ed175c8e610" |
| landingi.com | TXT | Text record | "79fd645f24e8e36c6248dd658c4cd9276eb8548fea9cc67bf8594a5e8af4d25" |
| landingi.com | TXT | Text record | "be771822252daf2997d6f7f36b4f21ac0e3a80a9f9ddb21e98576c8b1a9aa11" |
| landingi.com | TXT | Text record | "google-site-verification=EFeOD8kChicX646E_n79BGtS8u3HIlZxONqXV-39BEE" |
| landingi.com | TXT | Text record | "google-site-verification=wSYPJSWZgBDgoLKubvKLl2gcFBq5zCqF6UnHZqyZWQ8" |
| landingi.com | TXT | Text record | "hubspot-developer-verification=MWI0MTQ5M2YtNWUzMC00ZDU2LWJiNWEtNDFhMzIzZjUwMDNk" |
| landingi.com | TXT | Text record | "linkedin-site-verification=05810fab-b03c-42d9-b38e-cc2cce5fb319" |
| landingi.com | TXT | Text record | "openai-domain-verification=dv-8el92sPGcGm6g2Q5W0PWYVcS" |
| landingi.com | TXT | Text record | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;" |
| landingi.com | TXT | Text record | "zoom-domain-verification = 658fec25-3a44-4611-ae2a-48a10cdcf029" |
| landingi.com | SPF | Sender Policy Framework | "v=spf1 include:spf.mandrillapp.com include:spf.braintreegateway.com include:1203222.spf08.hubspotemail.net include:_spf.google.com include:_spf.mlsend.com -all" |
| landingi.com | CAA | Certificate Authority Authorization | 0 issue "amazon.com" |
| landingi.com | CAA | Certificate Authority Authorization | 0 issue "amazonaws.com" |
| landingi.com | CAA | Certificate Authority Authorization | 0 issue "amazontrust.com" |
| landingi.com | CAA | Certificate Authority Authorization | 0 issue "awstrust.com" |
| landingi.com | CAA | Certificate Authority Authorization | 0 issue "certum.pl" |
| landingi.com | CAA | Certificate Authority Authorization | 0 issue "digicert.com" |
| landingi.com | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
| _dmarc.landingi.com | TXT | Text record | "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@landingi.com; sp=quarantine; aspf=r;" |
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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCIkCt/mgHJhzwlYjEzVj+yu3AkhBWr121CCFEeakHQ3ohev8wIu+ao60NqQKvZZIx0DQUc3v3sj+UdPN2uVUVBpBRsfv6h31XTUhlf3W4MbZNSJ3dXwgUh/Dvm7ShkTHrxXxPIVv7/oCD6NRWMmS78rbStOULL9YRFavED1UtY2wIDAQAB" | |
| k1 | rsa | 1296 | "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;" |
| mailjet | rsa | 1296 | "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCVVbkqqnSX97tGVNOxewkJz4vKsW/NX1sT4j3vxf3aYtknANWh5X/8XHyK2P+DDp+CWZNVzYKdgk41E1odpcn2g/RGLfUQa+GOYe6dQI6pzSadQlFIKn3FYjN8LI7K2t3OVXOvQ17h4yh6Mo63nsyVXTEBjLMQSLm3Ld58JqBx2QIDAQAB" |
| mandrill | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;" |
| smtpapi | rsa | 1296 | "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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 |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| landingi.com | SPF | Sender Policy Framework | "v=spf1 include:spf.mandrillapp.com include:spf.braintreegateway.com include:1203222.spf08.hubspotemail.net include:_spf.google.com include:_spf.mlsend.com -all" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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 | CMS, Blogs |
| WordPress Site Editor | Page builders |
| WordPress Block Editor | Page builders |
| MySQL | Databases |
| PHP | Programming languages |
| Autoptimize 3.1.15.1 | WordPress plugins, Performance |
| WPML 4.6.9 | WordPress plugins, Translation |
| cdnjs | CDN |
| Cloudflare Bot Management | Security |
| Kinsta | PaaS, Hosting |
| Cloudflare | CDN |
| HTTP/3 | 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 |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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 |
|---|---|
| Cloudflare Bot Management | Security |
| Cloudflare | CDN |
| HTTP/3 | 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.