CVE-2024-38971: vaeThink 1.0.2 is vulnerable to stored Cross Site Scripting (XSS) in the system backend.

Routine

MEDIUM 5.4DOWNGRADE

CVE-2024-38971 is a medium-severity flaw (CVSS 5.4) affecting vaethink. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

vaeThink 1.0.2 is vulnerable to stored Cross Site Scripting (XSS) in the system backend.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-79
Published	2024-07-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: vaethink

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

Am I affected?

Timeline

2024-07-09 18:15 UTCPublished CVE record published
2026-06-17 07:41 UTCUpdated Record last modified

vaethink vaethink DOWNGRADE

Affected: 1.0.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.2

1. Check installed version

apt-cache policy vaethink || rpm -q vaethink || vaethink --version

2. No fixed release: DOWNGRADE to a release before 1.0.2 (Debian / Ubuntu)

apt-cache madison vaethink sudo apt install vaethink=<VERSION_BEFORE_1.0.2> sudo apt-mark hold vaethink

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vaethink sudo dnf downgrade vaethink-<VERSION_BEFORE_1.0.2> sudo dnf versionlock add vaethink

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-38971?

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

Is CVE-2024-38971 being exploited?

CVE-2024-38971 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-38971 affect?

CVE-2024-38971 affects vaethink. Severity is medium (CVSS 5.4). vaeThink 1.0.2 is vulnerable to stored Cross Site Scripting (XSS) in the system backend.

How urgent is CVE-2024-38971?

Priority 24/100. No elevated risk signals yet.

Related CVEs

CVE-2024-38970 MEDIUM 4.9 DOWNGRADE vaeThink 1.0.2 is vulnerable to Information Disclosure via the system backend,access management administrator

References

← Back to latest CVEs