Skip to main content

Security report for concretecms.org

PortlandLabs · Technology · N/a

Low risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

79/100

Risk levelLow

0–100, higher is better. How it is calculated

Concrete CMS is an open source content management system developed and maintained by PortlandLabs. It offers a user-friendly, extendable platform designed for both developers and content editors, emphasizing ease of use and flexibility. The website positions Concrete CMS as a trusted solution used by governments and Fortune 500 companies, distributed under the MIT license. The business model revolves around open source software with community engagement and commercial support options. Technically, the website leverages modern web technologies including jQuery, Bootstrap, Vue.js, and FontAwesome, with analytics powered by Matomo and Google Analytics. The site is mobile optimized and demonstrates good SEO and accessibility practices, though some accessibility features could be enhanced. Performance is moderate with room for improvement in loading speed and technical modernization. From a security perspective, the site enforces HTTPS and provides a dedicated security page, along with cookie consent mechanisms compliant with GDPR. However, explicit security headers are not detected, and there is no public vulnerability disclosure or incident response contact information. No vulnerabilities or exposed sensitive data were found in the analysis. Overall, the website is professional, trustworthy, and well-maintained, with a strong focus on user experience and compliance. The lack of WHOIS data is mitigated by the presence of privacy protection, which is justified for this type of open source project. Strategic recommendations include enhancing security headers, publishing vulnerability disclosure policies, and providing clearer incident response contacts to further strengthen trust and security posture.

Scanned

This is an earlier scan of concretecms.org. View the latest report

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

3 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching concretecms.org

This scan found 16 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
100
Security headers
65
Email security
70
DNS health
85
Network security
100
GDPR outside view
53
Average
79

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Concrete CMS occupies a niche in the open source CMS market, competing by offering a balance of developer flexibility and editor usability. Its open source MIT license encourages adoption and community contributions, while PortlandLabs provides commercial support and hosting guidance. The target customers include developers, agencies, and organizations seeking a customizable CMS with a strong community backing. The presence of testimonials and trusted clients indicates a positive market reputation. The ecosystem includes a marketplace for add-ons and themes, fostering an extensible platform. Growth potential lies in expanding community engagement and commercial partnerships. The company operates in the technology sector with a medium-sized footprint. Its digital presence is well-structured, leveraging multiple subdomains for documentation, forums, and community engagement. The absence of direct contact emails or phone numbers on the main site suggests a preference for managed contact via forms and community channels.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS and a dedicated security information page. Cookie consent and privacy policies align with GDPR requirements, indicating compliance awareness. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options represents an area for improvement. No public vulnerability disclosure or security.txt file was found, which could enhance transparency and incident response readiness. No signs of vulnerabilities or exposed sensitive data were detected. Overall, the security posture is solid but could benefit from additional hardening and published security processes.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to mitigate common web attacks.
  2. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting and improve transparency.
  3. Provide clear incident response contact information, such as a dedicated security email address, to enhance trust and readiness.
  4. Optimize website performance by improving loading speed and modernizing technical stack components.
  5. Enhance accessibility features to meet higher standards and improve usability for all users.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PortlandLabs
Description
Concrete CMS is an open source content management system that provides a point and click, free CMS to create websites. It is designed as an extendable platform with built-in features, trusted by governments and Fortune 500 companies.
Key services
CMS software, Hosting guidance, Extensions marketplace, Community support
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Bootstrap, FontAwesome, Matomo Analytics, Vue.js
Frameworks
Concrete CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Security page linked
  • Cookie consent banner

Analytics and tracking

Services
Matomo, Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is rich, professional, and well-structured.
  3. Strong presence of trust indicators including testimonials and security page.
  4. No direct contact emails or phone numbers found on the homepage; contact is via form.
  5. WHOIS data is unavailable, likely due to privacy protection or query error.
  6. Use of modern web technologies and analytics tools.
  7. Cookie consent and privacy policy are implemented and GDPR compliant.
Technical notes

Notes

The website is built on Concrete CMS, utilizing a combination of jQuery, Bootstrap, Vue.js, and FontAwesome for frontend functionality and styling. Analytics are handled via Matomo and Google Analytics, indicating a balanced approach to user tracking and privacy. The site is mobile responsive with good SEO metadata and Open Graph tags. Performance is moderate, with potential improvements in asset loading and caching. The technical implementation is modern but could benefit from updated accessibility practices and additional security hardening. Hosting details are not explicitly identified, but the presence of portlandlabs.com analytics suggests hosting or operational ties to PortlandLabs.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 79/100Low24 findingsView report
Reviews of this site

Share your experience with concretecms.org. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review concretecms.org.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.