CVE-2011-3811: TomatoCart 1.1.3 allows remote attackers to obtain sensitive information via a direct request to a .php file,

Routine

MEDIUM 5.0DOWNGRADE

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

TomatoCart 1.1.3 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 templates/system/offline.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: tomatocart

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

tomatocart tomatocart DOWNGRADE

Affected: 1.1.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.1.3

1. Check installed version

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

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

apt-cache madison tomatocart sudo apt install tomatocart=<VERSION_BEFORE_1.1.3> sudo apt-mark hold tomatocart

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

dnf --showduplicates list tomatocart sudo dnf downgrade tomatocart-<VERSION_BEFORE_1.1.3> sudo dnf versionlock add tomatocart

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

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

Is CVE-2011-3811 being exploited?

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

CVE-2011-3811 affects tomatocart. Severity is medium (CVSS 5.0). TomatoCart 1.1.3 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 templates/system/offline.php and certain other files.

How urgent is CVE-2011-3811?

Priority 35/100. No elevated risk signals yet.

Software pages

PHP vulnerabilities

Related CVEs

CVE-2014-3978 MEDIUM 6.5 DOWNGRADE SQL injection vulnerability in TomatoCart 1.1.8.6.1 allows remote authenticated users to execute arbitrary SQL
CVE-2014-3830 MEDIUM 4.3 DOWNGRADE Cross-site scripting (XSS) vulnerability in info.php in TomatoCart 1.1.8.6.1 allows remote attackers to inject
CVE-2012-5907 MEDIUM 5.0 DOWNGRADE Directory traversal vulnerability in json.php in TomatoCart 1.2.0 Alpha 2 and possibly earlier allows remote a
CVE-2012-4934 LOW 3.5 DOWNGRADE TomatoCart 1.1.7, when the PayPal Express Checkout module is enabled in sandbox mode, allows remote authentica

References

← Back to latest CVEs