Vulnerability Scan Result
| Title: | Risebeyond Ministry – Raises Voices, Restoring Hope, Building Legacy, Rising Beyond |
| Description: | RiseXpressionzz Gospel Radio broadcasts uplifting gospel music, worship, encouragement, and spiritual inspiration — streaming live 24/7 from RiseBeyond Ministry. |
| ip_address | 192.0.78.240 |
| country | US  |
| network_name | Automattic, Inc. |
| asn | AS2635 |
| ip_address | 192.0.78.182 |
| country | US |
| network_name | Automattic, Inc. |
| asn | AS2635 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Gutenberg | WordPress plugins, Editors |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.39.0 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| Jetpack | WordPress plugins |
| jQuery 3.7.1 | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React 18.3.1 | JavaScript frameworks |
| Swiper | JavaScript libraries |
| Priority Hints | Performance |
| WordPress.com | PaaS |
| WordPress | CMS, Blogs |
| WordPress Site Editor | Page builders |
| WordPress Block Editor | Page builders |
| HSTS | Security |
| RSS | Miscellaneous |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Gutenberg | WordPress plugins, Editors |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| core-js 3.39.0 | JavaScript libraries |
| HTTP/3 | Miscellaneous |
| Jetpack | WordPress plugins |
| jQuery 3.7.1 | JavaScript libraries |
| Moment.js 2.30.1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React 18.3.1 | JavaScript frameworks |
| Swiper | JavaScript libraries |
| Priority Hints | Performance |
| WordPress.com | PaaS |
| WordPress | CMS, Blogs |
| WordPress Site Editor | Page builders |
| WordPress Block Editor | Page builders |
| HSTS | Security |
| RSS | 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://risebeyondministry.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 | Evidence |
|---|---|
| https://risebeyondministry.org/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://risebeyondministry.org/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://risebeyondministry.org/wp-json/wp/v2 | 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 | Possible API endpoint found at |
| https://risebeyondministry.org/xmlrpc.php | GET | Query: rsd= 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 | Possible API endpoint found at |
Vulnerability description
We found API endpoints while crawling the given web application.
Risk description
These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.
Recommendation
Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns3.wordpress.com, ns2.wordpress.com, ns1.wordpress.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 |
|---|---|---|---|
| risebeyondministry.org | SPF | Sender Policy Framework | "v=spf1 include:_spf.wpcloud.com ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| risebeyondministry.org | A | IPv4 address | 192.0.78.240 |
| risebeyondministry.org | A | IPv4 address | 192.0.78.182 |
| risebeyondministry.org | NS | Name server | ns3.wordpress.com |
| risebeyondministry.org | NS | Name server | ns2.wordpress.com |
| risebeyondministry.org | NS | Name server | ns1.wordpress.com |
| risebeyondministry.org | SOA | Start of Authority | ns1.wordpress.com. hostmaster.wordpress.com. 2026043001 14400 7200 604800 300 |
| risebeyondministry.org | SPF | Sender Policy Framework | "v=spf1 include:_spf.wpcloud.com ~all" |
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 |
|---|---|
| WordPress | CMS, Blogs |
| WordPress Site Editor | Page builders |
| WordPress Block Editor | Page builders |
| Gutenberg | WordPress plugins, Editors |
| MySQL | Databases |
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| WordPress.com | PaaS |
| Moment.js | JavaScript libraries |
| jQuery Migrate | JavaScript libraries |
| jQuery | JavaScript libraries |
| HSTS | Security |
| HTTP/3 | Miscellaneous |
| Underscore.js 1.13.7 | JavaScript libraries |
| Clipboard.js | JavaScript libraries |
| Jetpack | 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
| Operating System | Accuracy |
|---|---|
| IPCop 2.0 (Linux 2.6.32) | 97% |
Vulnerability description
OS Detection