CVE-2024-6941: A vulnerability, which was classified as problematic, has been found in ThinkSAAS 3.7.0

Routine

LOW 3.5DOWNGRADE

CVE-2024-6941 is a low-severity flaw (CVSS 3.5) affecting thinksaas. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability, which was classified as problematic, has been found in ThinkSAAS 3.7.0. This issue affects some unknown processing of the file app/system/action/do.php. The manipulation of the argument site_title/site_subtitle/site_key/site_desc/site_url/site_email/site_icp leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerabi

Why this priority

Public exploit reference

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

Risk facts

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

Publisher (CNA): VulDB · Vendor: thinksaas

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

Am I affected?

Timeline

2024-07-21 06:15 UTCPublished CVE record published
2026-06-17 08:19 UTCUpdated Record last modified

thinksaas thinksaas DOWNGRADE

Affected: 3.70

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.70

1. Check installed version

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

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

apt-cache madison thinksaas sudo apt install thinksaas=<VERSION_BEFORE_3.70> sudo apt-mark hold thinksaas

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

dnf --showduplicates list thinksaas sudo dnf downgrade thinksaas-<VERSION_BEFORE_3.70> sudo dnf versionlock add thinksaas

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

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

Is CVE-2024-6941 being exploited?

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

CVE-2024-6941 affects thinksaas. Severity is low (CVSS 3.5). A vulnerability, which was classified as problematic, has been found in ThinkSAAS 3.7.0. This issue affects some unknown processing of the file app/system/action/do.php. The manipulation of the argument site_title/site_subtitle/site_key/sit

How urgent is CVE-2024-6941?

Priority 27/100. Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2024-6942 LOW 3.5 DOWNGRADE A vulnerability, which was classified as problematic, was found in ThinkSAAS 3.7.0
CVE-2024-40456 CRITICAL 9.8 DOWNGRADE ThinkSAAS v3.7.0 was discovered to contain a SQL injection vulnerability via the name parameter at \system\act
CVE-2024-40455 LOW 2.7 DOWNGRADE An arbitrary file deletion vulnerability in ThinkSAAS v3.7 allows attackers to delete arbitrary files via a cr
CVE-2024-33102 MEDIUM 5.4 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in the component /pubs/counter.php of ThinkSAAS v3.7.0 allow
CVE-2024-33101 MEDIUM 6.1 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in the component /action/anti.php of ThinkSAAS v3.7.0 allows

References

← Back to latest CVEs