Skip to main content
VulnerabilityPublished Updated

CVE-2024-53484: ever-traduora · Use of Hard-coded Credentials

Affects ever-traduoraSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubever-co/ever-traduorapkg:github/ever-co/ever-traduoraOther threatsAffected
  • <=0.20.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately replace the hard-coded JWT signing key with a securely generated, unique secret for each deployment.
  2. Implement environment-based configuration for JWT keys rather than embedding them in source code.
  3. Rotate existing JWT keys and invalidate all existing tokens to prevent misuse.
  4. Apply the latest patches or updates from the vendor as soon as they become available.
  5. Conduct a thorough audit of JWT usage and authentication flows to ensure no other hard-coded secrets exist.
  6. Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) to detect and block suspicious JWT token usage.
  7. Educate development teams on secure credential management practices to prevent recurrence of hard-coded secrets.
  8. Monitor logs for unusual authentication activity that may indicate exploitation attempts.

Description

Ever Traduora 0.20.0 and below is vulnerable to Privilege Escalation due to the use of a hard-coded JWT signing key.

References

Community reviews

Loading reviews…