CVE-2022-25578
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
9.8
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
- Record
CVE-2022-25578- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-94
- Updated
- 2026-11-02
CVE List No score
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
- Record
CVE-2022-25578- Updated
- 2026-11-02
EUVDEUVD-2022-30239 No score
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
- Record
EUVD-2022-30239- Updated
- 2026-11-02
GitHub AdvisoriesGHSA-fg7x-cw25-mq65
9.8
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
- Record
GHSA-fg7x-cw25-mq65- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-94
- Updated
- 2026-11-02
OSV No score
taocms v3.0.2 allows attackers to execute code injection via arbitrarily editing the .htaccess file.
- Record
CVE-2022-25578- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2022-25578 is a critical vulnerability (CVSS 9.8) in Taogogo Taocms, published March 18, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.80%, the 78th percentile. No source names a fixed version.