Vulnerability Scan Result
| Title: | The Richmond Film Network |
| Description: | The Richmond Film Network is your go-to hub for filmmakers, storytellers, and screen-based media creatives in all disciplines. Whether you're behind the camera, in front of it, or working behind the scenes, we're here to connect you with collaborators, resources, and opportunities to bring your creative visions to life. From screenwriters to gaffers, actors to audio engineers—if you're part of the independent filmmaking world, this is your community. |
| ip_address | 162.159.128.53 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 162.159.138.52 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
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-alt | cloudflare - |
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Amazon Web Services | PaaS |
| Backbone.js 1.1.2 | JavaScript frameworks |
| Linkedin Insight Tag | Analytics |
| Ethers | JavaScript libraries |
| Font Awesome | Font scripts |
| Froala Editor 2+ | Rich text editors |
| jQuery Migrate 3.0.1 | JavaScript libraries |
| Google Analytics | Analytics |
| Handlebars 4.7.7 | JavaScript frameworks |
| Imgix | CDN, Digital asset management |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.11.0 | JavaScript libraries |
| Marionette.js | JavaScript frameworks |
| Moment.js 2.30.1 | JavaScript libraries |
| Material UI | UI frameworks |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Pusher | Live chat |
| React | JavaScript frameworks |
| React Router 6 | JavaScript frameworks |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Statsig | Analytics, Feature management |
| Google Ads Conversion Tracking | Analytics |
| TrackJs | Analytics |
| Underscore.js | JavaScript libraries |
| PWA | Miscellaneous |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| Lodash 1.13.7 | JavaScript libraries |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2021-41184 | 6.5 | 0.25367 | 0.96227 | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources. |
| CVE-2021-41183 | 6.5 | 0.02921 | 0.86442 | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML. A workaround is to not accept the value of the `*Text` options from untrusted sources. |
| CVE-2021-41182 | 6.5 | 0.27509 | 0.96444 | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources. |
| CVE-2022-31160 | 6.1 | 0.10183 | 0.93154 | jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`. |
| CVE-2016-7103 | 6.1 | 0.01397 | 0.80488 | Cross-site scripting (XSS) vulnerability in jQuery UI before 1.12.0 might allow remote attackers to inject arbitrary web script or HTML via the closeText parameter of the dialog function. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. 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
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| 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 | Evidence |
|---|---|
| https://members.richmondfilmnetwork.org/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Amazon Web Services | PaaS |
| Backbone.js 1.1.2 | JavaScript frameworks |
| Linkedin Insight Tag | Analytics |
| Ethers | JavaScript libraries |
| Font Awesome | Font scripts |
| Froala Editor 2+ | Rich text editors |
| jQuery Migrate 3.0.1 | JavaScript libraries |
| Google Analytics | Analytics |
| Handlebars 4.7.7 | JavaScript frameworks |
| Imgix | CDN, Digital asset management |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.11.0 | JavaScript libraries |
| Marionette.js | JavaScript frameworks |
| Moment.js 2.30.1 | JavaScript libraries |
| Material UI | UI frameworks |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Pusher | Live chat |
| React | JavaScript frameworks |
| React Router 6 | JavaScript frameworks |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Statsig | Analytics, Feature management |
| Google Ads Conversion Tracking | Analytics |
| TrackJs | Analytics |
| Underscore.js | JavaScript libraries |
| PWA | Miscellaneous |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| Lodash 1.13.7 | JavaScript libraries |
| 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 |
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 |
|---|---|
| Ruby | Programming languages |
| PHP | Programming languages |
| Ruby on Rails | Web frameworks |
| Material UI | UI frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Cloudflare Bot Management | Security |
| reCAPTCHA | Security |
| Linkedin Insight Tag | Analytics |
| HSTS | Security |
| Cloudflare | CDN |
| Google Ads | Advertising |
| TrackJs | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
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 Browser Insights | Analytics, RUM |
| Cloudflare Bot Management | Security |
| HSTS | Security |
| Cloudflare | CDN |
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 |
|---|---|
| Ruby | Programming languages |
| PHP | Programming languages |
| Ruby on Rails | Web frameworks |
| Material UI | UI frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Cloudflare Bot Management | Security |
| reCAPTCHA | Security |
| Linkedin Insight Tag | Analytics |
| HSTS | Security |
| Cloudflare | CDN |
| Google Ads | Advertising |
| TrackJs | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
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 |
|---|---|
| PHP | Programming languages |
| Ruby | Programming languages |
| Material UI | UI frameworks |
| Ruby on Rails | Web frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| reCAPTCHA | Security |
| Linkedin Insight Tag | Analytics |
| HSTS | Security |
| Cloudflare | CDN |
| Google Ads | Advertising |
| TrackJs | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| 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.
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare Bot Management | Security |
| HSTS | Security |
| Cloudflare | CDN |
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 |
|---|---|
| PHP | Programming languages |
| Ruby | Programming languages |
| Material UI | UI frameworks |
| Ruby on Rails | Web frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| reCAPTCHA | Security |
| Linkedin Insight Tag | Analytics |
| HSTS | Security |
| Cloudflare | CDN |
| Google Ads | Advertising |
| TrackJs | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| 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.
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-RELEASE | 91% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Ruby | Programming languages |
| Material UI | UI frameworks |
| Ruby on Rails | Web frameworks |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| reCAPTCHA | Security |
| Linkedin Insight Tag | Analytics |
| HSTS | Security |
| Cloudflare | CDN |
| Google Ads | Advertising |
| TrackJs | Analytics |
| Google Ads Conversion Tracking | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| 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.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| members.richmondfilmnetwork.org | A | IPv4 address | 162.159.128.53 |
| members.richmondfilmnetwork.org | A | IPv4 address | 162.159.138.52 |
| members.richmondfilmnetwork.org | CNAME | Canonical name | ssl.mn.co |
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
| Software / Version | Category |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare Bot Management | Security |
| HSTS | Security |
| Cloudflare | CDN |
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.