CVE-2011-3812: Vanilla 2.0.16 allows remote attackers to obtain sensitive information via a direct request to a .php file, wh

Routine

MEDIUM 5.0DOWNGRADE

CVE-2011-3812 is a medium-severity flaw (CVSS 5.0) affecting vanilla. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Vanilla 2.0.16 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by plugins/Minify/min/utils.php and certain other files.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Weakness	CWE-200
Published	2011-09-24
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: vanillaforums

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

Am I affected?

Timeline

2011-09-24 00:55 UTCPublished CVE record published
2026-06-16 23:33 UTCUpdated Record last modified

vanillaforums vanilla DOWNGRADE

Affected: 2.0.16

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.16

1. Check installed version

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

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

apt-cache madison vanilla sudo apt install vanilla=<VERSION_BEFORE_2.0.16> sudo apt-mark hold vanilla

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

dnf --showduplicates list vanilla sudo dnf downgrade vanilla-<VERSION_BEFORE_2.0.16> sudo dnf versionlock add vanilla

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-2011-3812?

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

Is CVE-2011-3812 being exploited?

CVE-2011-3812 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-2011-3812 affect?

CVE-2011-3812 affects vanilla. Severity is medium (CVSS 5.0). Vanilla 2.0.16 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by plugins/Minify/min/utils.php and certain other files.

How urgent is CVE-2011-3812?

Priority 35/100. No elevated risk signals yet.

Software pages

PHP vulnerabilities

Related CVEs

CVE-2020-8825 MEDIUM 5.4 DOWNGRADE index.php?p=/dashboard/settings/branding in Vanilla 2.6.3 allows stored XSS.
CVE-2019-9889 LOW 2.7 UPGRADE In Vanilla before 2.6.4, a flaw exists within the getSingleIndex function of the AddonManager class
CVE-2018-19499 HIGH 7.2 UPGRADE Vanilla before 2.5.5 and 2.6.x before 2.6.2 allows Remote Code Execution because authenticated administrators
CVE-2018-18903 CRITICAL 9.8 UPGRADE Vanilla 2.6.x before 2.6.4 allows remote code execution.
CVE-2018-17571 MEDIUM 6.1 UPGRADE Vanilla before 2.6.1 allows XSS via the email field of a profile.

References

← Back to latest CVEs