Security - https://weblate.org BeaverCheck Audit

C

Permissions-Policy

Action

1 directives, 5 missing

REVIEW

1 directives, 5 missing

interest-cohort=() — blocked for all origins

camera not restricted

Consider adding camera=() to block camera access from embedded content.

microphone not restricted

Consider adding microphone=() to block microphone access from embedded content.

geolocation not restricted

Consider adding geolocation=() to block geolocation access from embedded content.

payment not restricted

Consider adding payment=() to block payment access from embedded content.

usb not restricted

Consider adding usb=() to block usb access from embedded content.

Raw Header

interest-cohort=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

interest-cohort Blocked

camera Not Set

microphone Not Set

geolocation Not Set

payment Not Set

usb Not Set

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

No CORS headers present — secure default

CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control

A+

Security Headers

9 of 10 headers properly configured

PASS

9 of 10 headers properly configured

Strict-Transport-Security is properly configured

Got: max-age=31536000; includeSubDomains; preload

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: DENY

Referrer-Policy is properly configured

Got: same-origin

Permissions-Policy is set

Got: interest-cohort=()

Content-Security-Policy is present

Got: default-src 'self'; style-src 'self'; img-src 'self' data: hosted.weblate.org bl…

Cross-Origin-Opener-Policy is properly configured

Got: same-origin

Cross-Origin-Embedder-Policy header is missing

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

X-Powered-By header is not present

Server header is present without version info

Got: nginx

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

A

Content Security Policy

7 of 10 CSP checks passed

PASS

7 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'self'; style-src 'self'; img-src 'self' data: hosted.weblate.org blog.cihar.com gate.thepay.cz *.githubusercontent.com; script-src 'self' browser.sentry-cdn.com de.sentry.io; connect-src 'self' de.sentry.io; object-src 'none'; font-src 'self'; frame-src 'none'; frame-ancestors 'none'; form-action 'self' weblate.org hosted.weblate.org gate.thepay.cz thepay.cz;report-uri https://o4507304895905792.ingest.de.sentry.io/api/4507486269866064/security/?sentry_key=5eb5194266692a262a4f8a6aad7a25b6

default-src directive is set

Got: default-src 'self'

No 'unsafe-inline' in script source

No 'unsafe-eval' in script source

No wildcard in script source

object-src is set to 'none'

Got: object-src 'none'

base-uri directive is missing

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

frame-ancestors directive is set

Got: frame-ancestors 'none'

form-action directive is set

Got: form-action 'self' weblate.org hosted.weblate.org gate.thepay.cz thepay.cz

upgrade-insecure-requests is not set

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'

Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

default-src 'self'

style-src 'self'

img-src 'self'data:hosted.weblate.orgblog.cihar.comgate.thepay.cz*.githubusercontent.com

script-src 'self'browser.sentry-cdn.comde.sentry.io

connect-src 'self'de.sentry.io

object-src 'none'

font-src 'self'

frame-src 'none'

frame-ancestors 'none'

form-action 'self'weblate.orghosted.weblate.orggate.thepay.czthepay.cz

report-uri https://o4507304895905792.ingest.de.sentry.io/api/4507486269866064/security/?sentry_key=5eb5194266692a262a4f8a6aad7a25b6

A+

TLS & Certificates

TLS 1.3, 7 checks passed

PASS

TLS 1.3, 7 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_AES_128_GCM_SHA256

HTTP/2 is not negotiated

HTTP/2 provides multiplexing and header compression for better performance.

Got: http/1.1

Certificate is valid (expires in 81 days)

Got: 2026-07-13T07:35:20Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 2 domain(s)

Got: weblate.org, www.weblate.org

Certificate is issued by a trusted CA

Got: CN=R12,O=Let's Encrypt,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_AES_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=weblate.orgIssuer CN=R12,O=Let's Encrypt,C=USValid 2026-04-14T07:35:21Z → 2026-07-13T07:35:20ZExpires in 81 days SANs weblate.org, www.weblate.orgSignature SHA256-RSASerial 5f146c554c79fe3ad09fb41b16f9426a194

Intermediate (CA Certificate)

Subject CN=R12,O=Let's Encrypt,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2024-03-13T00:00:00Z → 2027-03-12T23:59:59ZExpires in 324 days Signature SHA256-RSASerial c212324b70a9b49171dc40f7e285263c

A+

Cookie Security

No cookies set — no cookie security risks

PASS

No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+

Subresource Integrity

No external resources

PASS

No external resources

No external resources to protect

SRI Coverage No external resources — SRI not applicable

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

security.txt is present — good practice

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✗ Exposed	Security Policy	Info

A+

Email Security

DMARC: reject

PASS

DMARC: reject

DMARC policy is reject — strongest protection

DMARC

Policy reject — strongest protection Record v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; pct=100; fo=1:d:s; rua=mailto:a0dd847bdb1843c9934469b693920d7b@dmarc-reports.cloudflare.net;

A+

security.txt

Signed, 3 contact(s) — RFC 9116 compliant

PASS

security.txt

Contact: mailto:security@weblate.org, https://github.com/WeblateOrg/weblate/security/advisories/new, https://hackerone.com/weblate

Encryption: https://weblate.org/.well-known/openpgpkey/hu/t5s8ztdbon8yzntexy6oz5y48etqsnbb

Policy: https://weblate.org/.well-known/security.txt

A

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) not advertised

HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.

HSTS enabled (includeSubDomains, preload)

HSTS preload enabled

TLS 1.3 in use (fastest handshake, 1-RTT)