current.finance

https://current.finance
dApp frontend · scanned 2 h ago

Findings

  • medium No Content-Security-Policy
    The site sends no Content-Security-Policy, so an injected script (XSS, compromised dependency) runs with full access to the wallet UI.
  • medium No HTTP Strict Transport Security
    Browsers are not told to always use HTTPS, so a network attacker can downgrade the first visit and swap the front end.
  • medium Page can be framed (clickjacking)
    Any site can embed this page in a frame, so users can be tricked into clicking wallet-connect or approval buttons.
  • low DNSSEC not enabled
    DNS answers for the domain are not signed, so a resolver-level attacker could redirect users to a fake front end.
  • low No Referrer-Policy
    Full page URLs (which can carry addresses or tokens) may be sent to third-party sites in the Referer header.
  • info No CAA record
    Any certificate authority may issue certificates for the domain.
  • info No Permissions-Policy
    The site does not restrict powerful browser features (camera, microphone, payment, USB) for itself and embedded frames.

Evidence, exact locations and fixes are in the deep report. How scoring works.

Scan notes

Script https://www.current.finance/assets/index-2XDhZ0ml.js truncated at 200 KB.

Get the full picture

Evidence, locations, fixes and an AI code review. Private link, no email.

For the team behind it: prove ownership and add active checks.

Paid in crypto via NOWPayments. Automated pre-audit, not an audit.

Facts

Hosting
Cloudflare
DNS provider
Cloudflare
DNSSEC
No
HTTPS
Yes
HSTS
No
CSP
No
Wallet SDKs
None detected
Third-party scripts
0
Scripts scanned
1
security.txt
Yes
robots.txt
Yes

Badge

DappVet score 77

[![Vetted by DappVet](https://dappvet.com/badge/AlVnStba.svg)](https://dappvet.com/d/current.finance)

Share on X

Changed something?

Scores refresh every 6 hours. Rescan now to pick up a fix.