Skip to main content

Security report for classicpress.net

ClassicPress · Technology · N/a

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

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

ClassicPress is a community-driven open source content management system forked from WordPress 4.9, targeting users who prefer the classic WordPress editor experience. It positions itself as a lightweight, stable, and familiar CMS alternative, supported by a small but active volunteer community and nonprofit governance. The website offers resources including plugins, themes, documentation, and community support channels such as forums and chat. The project is sponsored by several infrastructure partners and funded via donations. Technically, the site runs on a ClassicPress CMS compatible with WordPress 6.2.6, leveraging LiteSpeed caching technology and modern HTML5 standards, resulting in fast performance and good mobile and accessibility support. Security posture is solid with HTTPS enforced and no visible vulnerabilities, though explicit security headers and incident response policies are absent. Privacy compliance is good with a comprehensive privacy policy but lacks a cookie consent mechanism. WHOIS data is missing or unavailable, which reduces domain trustworthiness despite the legitimate and professional web presence. Overall, ClassicPress represents a credible niche open source CMS project with room for improvement in security transparency and domain registration clarity.

Scanned

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

4 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

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching classicpress.net

This scan found 21 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. The full timeline opens with your unlock code.

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
75
Security headers
60
Email security
75
DNS health
75
Network security
100
GDPR outside view
53
Average
73

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

ClassicPress operates in the technology sector as an open source CMS alternative to WordPress, focusing on users who prefer the classic editor interface. Its business model is community and donation-driven, supported by sponsors and volunteers. The project targets website creators including professionals, hobbyists, and developers seeking a stable and lightweight CMS. The presence of official plugin and theme directories, documentation, and active community forums indicates a mature ecosystem. Partnerships with hosting and infrastructure providers enhance operational reliability. The lack of a parent company and small team size suggest a focused, grassroots operation. Growth potential lies in appealing to WordPress users disenchanted with newer editor paradigms. Strategic partnerships and community engagement are key competitive advantages.

Security posture

The website demonstrates a good security posture with HTTPS enabled and no exposed sensitive data or vulnerable libraries detected. However, the absence of explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options is a gap. No published security policy or incident response contact information was found, which limits transparency and preparedness perception. The lack of a vulnerability disclosure policy or security.txt file further reduces security maturity. Privacy compliance is supported by a comprehensive privacy policy but lacks a cookie consent mechanism, which is a GDPR compliance shortfall. Overall, the security posture is solid but could be enhanced by publishing formal policies and implementing additional HTTP security headers.

Recommendations

  1. Implement and publish a formal security policy and incident response contact information to improve transparency and readiness.
  2. Add HTTP security headers including Content Security Policy, HSTS, X-Frame-Options, and X-XSS-Protection to strengthen defense-in-depth.
  3. Introduce a cookie consent mechanism to comply fully with GDPR and enhance user privacy controls.
  4. Publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security culture.
  5. Verify and update WHOIS domain registration data to improve domain legitimacy and trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ClassicPress
Description
ClassicPress is a community-led open source content management system. A fork of WordPress 4.9, it retains the WordPress classic editor as the default option.
Key services
Content management system software, Plugins directory, Themes directory, Community support forums, Documentation
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.2.6 compatible (ClassicPress 2.4.1), PHP, LiteSpeed Cache (litespeed), HTML5, JavaScript, CSS
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by canonical URL and og:url https)
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries
  • No forms with sensitive inputs detected on homepage

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a community-led open source CMS forked from WordPress 4.9
  2. Content is well structured with clear navigation and calls to action
  3. No forms with sensitive data on homepage; contact form exists on contact page
  4. No visible tracking or advertising scripts detected
  5. Social media presence active on Twitter, Facebook, GitHub, Zulip, and forums
  6. Sponsors and infrastructure partners are clearly listed
  7. No explicit security or incident response policies published
  8. WHOIS data missing or unavailable, which is unusual for an active domain
Technical notes

Notes

The website is built on ClassicPress CMS, a fork of WordPress 4.9, running a compatible version 2.4.1 with WordPress 6.2.6 compatibility. It uses LiteSpeed Cache technology for performance optimization and loads fonts and images with lazy loading techniques. The site employs modern HTML5 standards and replaces obsolete JavaScript libraries with native or modern alternatives, improving load times and accessibility. The site is mobile responsive with good navigation clarity and SEO optimization. No third-party analytics or advertising scripts were detected, indicating minimal tracking. The technical stack is modern and well-maintained, with no visible technical debt or deprecated components. Hosting provider details are not explicitly identified but infrastructure sponsors suggest reliable hosting.
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

Reviews of this site

Share your experience with classicpress.net. 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 classicpress.net.

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.