Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-53591: An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force at

57
This week
CRITICAL 9.8REMOTEDOWNGRADE

CVE-2024-53591 is a critical-severity flaw (CVSS 9.8) affecting seclore. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force attack.

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.7% (top 48%)
CISA exploited listNo
WeaknessCWE-862
Published2025-04-18
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: seclore

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

seclore seclore DOWNGRADE
Affected: 3.27.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.27.5.0
1. Check installed version
apt-cache policy seclore || rpm -q seclore || seclore --version
2. No fixed release: DOWNGRADE to a release before 3.27.5.0 (Debian / Ubuntu)
apt-cache madison seclore sudo apt install seclore=<VERSION_BEFORE_3.27.5.0> sudo apt-mark hold seclore
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list seclore sudo dnf downgrade seclore-<VERSION_BEFORE_3.27.5.0> sudo dnf versionlock add seclore
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-53591?

seclore: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-53591 being exploited?

CVE-2024-53591 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-53591 affect?

CVE-2024-53591 affects seclore. Severity is critical (CVSS 9.8). An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force attack.

How urgent is CVE-2024-53591?

Priority 57/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.