Vulnerability Scan Result

Target:

https://colegionuevocampestre.phidias.co/

Scanned target: https://colegionuevocampestre.phidias.co/

Submitted: Jan 28, 2026 from CO

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Colegio Nuevo Campestre
Description:	No description found

IP Information

ip_address	52.6.196.152
country	US
network_name	Amazon.com, Inc.
asn	AS14618

ip_address	54.159.222.250
country	US
network_name	Amazon.com, Inc.
asn	AS14618

ip_address	44.214.113.102
country	US
network_name	Amazon.com, Inc.
asn	AS14618

Open Ports

80/tcp	http	awselb/2.0 -
443/tcp	https	Apache httpd -

Web Technologies

Software / Version	Category
Firebase	Databases, Development
core-js 3.6.5	JavaScript libraries
Google Font API	Font scripts
Apache HTTP Server	Web servers
PHP	Programming languages
Vue.js	JavaScript frameworks
PWA	Miscellaneous
jsDelivr	CDN
HSTS	Security

Web Application Vulnerabilities

Evidence

Software / Version	Category
Firebase	Databases, Development
core-js 3.6.5	JavaScript libraries
Google Font API	Font scripts
Apache HTTP Server	Web servers
PHP	Programming languages
Vue.js	JavaScript frameworks
PWA	Miscellaneous
jsDelivr	CDN
HSTS	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.

Evidence

URL Evidence

URL	Evidence
https://colegionuevocampestre.phidias.co/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. object-src: We recommend restricting object-src to 'none'.

https://colegionuevocampestre.phidias.co/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. object-src: We recommend restricting object-src to 'none'.

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

URL	Evidence
https://colegionuevocampestre.phidias.co/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

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://colegionuevocampestre.phidias.co/	`<input type="text" name="_width" id="autofocus" autofocus autocorrect="off" autocapitalize="off" spellcheck="false"> <input type="password" name="_height"> <input type="submit" value="Ingresar" class="primaryButton">`

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Infrastructure Vulnerabilities

Operating System	Accuracy
Linux 2.6.32 - 3.13	91%

Evidence

Software / Version	Category
Firebase	Databases, Development
PHP	Programming languages
Apache HTTP Server	Web servers
HSTS	Security
jsDelivr	CDN
Google Font API	Font scripts
PWA	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
colegionuevocampestre.phidias.co	A	IPv4 address	54.159.222.250
colegionuevocampestre.phidias.co	A	IPv4 address	52.6.196.152
colegionuevocampestre.phidias.co	A	IPv4 address	44.214.113.102
colegionuevocampestre.phidias.co	MX	Mail server	10 inbound.postmarkapp.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.