How severe is CVE-2008-3922?

No CVSS score has been assigned to CVE-2008-3922 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2008-3922?

Affected package information for CVE-2008-3922 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2008-3922?

No fixed version has been published for CVE-2008-3922 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2008-3922 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2008-3922, including 2 documented proof-of-concept exploits on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2008-3922?

CVE-2008-3922 has an EPSS (Exploit Prediction Scoring System) score of 91.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2008-3922?

CVE-2008-3922 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2008-3922?

CVE-2008-3922 affects telartis_bv awstats totals (5 versions, e.g. 1.0, 1.1, 1.11…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2008-3922 published, and has it been updated?

CVE-2008-3922 was published on September 4, 2008 and was last updated on April 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2008-3922

awstatstotals.php in AWStats Totals 1.0 through 1.14 allows remote attackers to execute arbitrary code via PHP sequences in the sort parameter, which is used by the multisort function…

Published

Sep 4, 2008

Updated

Apr 23, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

91.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

awstatstotals.php in AWStats Totals 1.0 through 1.14 allows remote attackers to execute arbitrary code via PHP sequences in the sort parameter, which is used by the multisort function when dynamically creating an anonymous PHP function.

Affected Products

1 product · 5 configurations

Application

awstats totalstelartis_bv

5 versions

1.01.11.111.131.14

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-17324webappsphp✓ Verified

AWStats Totals 1.14 multisort - Remote Command Execution (Metasploit)

by Metasploit · May 25, 2011

Exploit-DB Source

EDB-6368webappsphp✓ Verified

AWStats Totals 1.14 - 'AWStatstotals.php' Remote Code Execution

by Ricardo Almeida · Sep 5, 2008

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2008-3922 in your stack?

O3 detects CVE-2008-3922 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works