Vulnerability Scan Result
| Title: | Unlocking Platform Play at GIFT IFSC: IFSCA’s Move Towards a Liberal Framework | India Corporate Law |
| Description: | Summary: The IFSCA has introduced a framework for Third-Party Fund Management Services (TFMS) at GIFT IFSC, enabling external fund managers to launch |
| ip_address | 104.198.164.198 |
| country | US  |
| network_name | Google LLC |
| asn | AS396982 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
2222/tcp | ssh | ProFTPD mod_sftp - |
| Software / Version | Category |
|---|---|
| Contact Form 7 6.0.6 | WordPress plugins, Form builders |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| Stimulus | JavaScript frameworks |
| WordPress | CMS, Blogs |
| WordPress Multisite | Hosting |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| Yoast SEO 24.9 | SEO, WordPress plugins |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://corporate.cyrilamarchandblogs.com/2025/07/unlocking-platform-play-at-gift-ifsc-ifscas-move-towards-a-liberal-framework/ | 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
| Software / Version | Category |
|---|---|
| Contact Form 7 6.0.6 | WordPress plugins, Form builders |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| Stimulus | JavaScript frameworks |
| WordPress | CMS, Blogs |
| WordPress Multisite | Hosting |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| Yoast SEO 24.9 | 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
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.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://corporate.cyrilamarchandblogs.com/2025/07/unlocking-platform-play-at-gift-ifsc-ifscas-move-towards-a-liberal-framework/ | 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 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.
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-07-19 05:30 EEST Nmap scan report for corporate.cyrilamarchandblogs.com (104.198.164.198) Host is up (0.098s latency). rDNS record for 104.198.164.198: 198.164.198.104.bc.googleusercontent.com
PORT STATE SERVICE VERSION 2222/tcp open ssh ProFTPD mod_sftp (protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 2.00 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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Salesforce | CRM |
| Contact Form 7 6.0.6 | WordPress plugins, Form builders |
| Nginx | Web servers, Reverse proxies |
| Stimulus | JavaScript frameworks |
| Yoast SEO 24.9 | SEO, WordPress plugins |
| WordPress Multisite | Hosting |
| Salesforce Marketing Cloud Account Engagement | Marketing automation |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| core-js 3.39.0 | JavaScript libraries |
| reCAPTCHA | Security |
| Priority Hints | Performance |
| Google Font API | Font scripts |
| Font Awesome | Font scripts |
| HSTS | Security |
| RSS | Miscellaneous |
| Open Graph | Miscellaneous |
| WP Engine | PaaS, Hosting |
| Underscore.js 1.13.7 | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| corporate.cyrilamarchandblogs.com | A | IPv4 address | 104.198.164.198 |
| corporate.cyrilamarchandblogs.com | CNAME | Canonical name | lxbplatform.wpengine.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 |
|---|---|
| Crestron XPanel control system | 90% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Contact Form 7 6.0.6 | WordPress plugins, Form builders |
| Nginx | Web servers, Reverse proxies |
| Stimulus | JavaScript frameworks |
| Yoast SEO 24.9 | SEO, WordPress plugins |
| WordPress Multisite | Hosting |
| reCAPTCHA | Security |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| HSTS | Security |
| WP Engine | PaaS, Hosting |
| Google Font API | Font scripts |
| Font Awesome | Font scripts |
| 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.