Vulnerability Scan Result

Target:

https://uunal2fbackend.dev.chickenalert.camdvr.org/

Scanned target: https://uunal2fbackend.dev.chickenalert.camdvr.org/

Submitted: Jun 13, 2026 from ET

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Student Portal
Description:	Online student portal. Access courses, assignments, study materials, and the digital library.

IP Information

ip_address	15.204.209.18
country	US
network_name	Ovh Sas
asn	AS16276

Open Ports

22/tcp	ssh	OpenSSH 10.0p2 Debian 7~bpo12+1
25/tcp	smtp	Postfix smtpd -
80/tcp	http	- -
443/tcp	https	- -
587/tcp	smtp	Postfix smtpd -
993/tcp	imaps	- -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
Google Font API	Font scripts
particles.js	JavaScript graphics
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
Lucide	Font scripts
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Plausible	Analytics
DoubleClick Floodlight	Advertising
WordPress	CMS, Blogs
AMP	JavaScript frameworks
Format	CMS
Google AdSense	Advertising
Google Tag Manager	Tag managers
jsDelivr	CDN
HSTS	Security

Web Application Vulnerabilities

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Google Font API	Font scripts
particles.js	JavaScript graphics
Google Analytics GA4	Analytics
HTTP/3	Miscellaneous
Lucide	Font scripts
MySQL	Databases
Open Graph	Miscellaneous
PHP	Programming languages
Plausible	Analytics
DoubleClick Floodlight	Advertising
WordPress	CMS, Blogs
AMP	JavaScript frameworks
Format	CMS
Google AdSense	Advertising
Google Tag Manager	Tag managers
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.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://uunal2fbackend.dev.chickenalert.camdvr.org/	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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://uunal2fbackend.dev.chickenalert.camdvr.org/robots.txt

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
Missing: https://uunal2fbackend.dev.chickenalert.camdvr.org/.well-known/security.txt

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

Software / Version	Category
WordPress	CMS, Blogs
Format	CMS
MySQL	Databases
PHP	Programming languages
particles.js	JavaScript graphics
AMP	JavaScript frameworks
Amazon Web Services	PaaS
jsDelivr	CDN
Plausible	Analytics
Google Tag Manager	Tag managers
Google AdSense	Advertising
Lucide	Font scripts
Google Font API	Font scripts
Google Analytics GA4	Analytics
DoubleClick Floodlight	Advertising
HSTS	Security
Open Graph	Miscellaneous
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
uunal2fbackend.dev.chickenalert.camdvr.org	A	IPv4 address	15.204.209.18

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.