CVE-2009-3113
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnspecified vulnerability in OXID eShop Professional, Enterprise, and Community Edition before 4.1.2, 3.x, and 2.x allows remote attackers to gain write access to product reviews via a crafted parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOXID eShop suffers from an access control bypass allowing remote attackers to gain unauthorized write access to product reviews via a crafted parameter. This is an authorization flaw in the review submission functionality where the application fails to properly validate user permissions before allowing review modifications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.7.0.3<= 3.0.4.1= 4.0.0.0_13895= 4.0.0.0_13934= 4.0.0.0_14260= 4.0.0.1_14455= 4.0.0.2_14842= 4.0.0.2_14967= 4.0.1.0_15990= 4.1.0-17976= 4.1.1-18442= 4.1.2-18998CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate OXID eShop installation directoryCheck your web server document root for the OXID eShop installation. Look for files like version.php in the core directory, or check the admin panel under 'System -> Info' for the version number.Affected if Cannot locate version information or the installation is not OXID eShop
-
Identify the installed OXID eShop version numberOpen version.php in the core directory, or log into the admin panel and navigate to System Info or General Settings to find the exact version string (e.g., 2.7.0.3, 3.0.4, 4.0.0.0).Affected if Version matches <= 2.7.0.3, <= 3.0.4.1, or any of these specific builds: 4.0.0.0_13895, 4.0.0.0_13934, 4.0.0.0_14260, 4.0.0.1_14455, 4.0.0.2_14842, 4.0.0.2_14967, 4.0.1.0_15990, 4.1.0-17976, 4.1.1-18442, or 4.1.2-18998
-
Verify review module is accessibleCheck if the product review functionality is enabled on the storefront. Visit a product page and look for the review form, or check the admin panel under 'Customer Info -> Product Reviews' to confirm the review module is active.Affected if Review functionality is enabled and publicly accessible without authentication requirements
-
Confirm review write operations lack authorization checksExamine the review submission script (typically in the 'reviews' module or controller). Look for the function handling review saving/editing and verify whether it checks user permissions before allowing write operations.Affected if The review save/edit code does not validate user permissions before processing review modifications
You are affected if your OXID eShop version is <= 2.7.0.3, <= 3.0.4.1, or matches any of the specific 4.x build numbers listed, AND the review submission functionality is accessible without proper authorization controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to OXID eShop 4.1.2 or later which contains the security fix. As a temporary measure, implement input validation on review-related parameters and consider a WAF rule to block suspicious review submission patterns.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-3113 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-3113 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data