CVE-2012-5304
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 · uneditedStatic code injection vulnerability in administration/install.php in YVS Image Gallery allows remote attackers to inject arbitrary PHP code into functions/db_connect.php via unspecified vectors. NOTE: this is only a vulnerability when the administrator does not follow recommendations in the product's installation documentation.
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 confidenceThe admin/install.php script in YVS Image Gallery fails to properly sanitize user input during the installation process, allowing remote attackers to inject arbitrary PHP code that gets written directly to functions/db_connect.php. When this compromised file is subsequently included by the application, the injected code executes with web server privileges.
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 dataall versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Confirm YVS Image Gallery is installedCheck for the presence of the YVS Image Gallery application by looking for its typical directory structure (e.g., /admin/, /functions/, /images/) or identifying the application via web server directory listings or file system inspection.Affected if The application files exist on the server.
-
Verify admin/install.php existsLocate the admin/install.php script in the web root directory. Use file system inspection or an HTTP request to check if the file is accessible (e.g., GET request to http://target/admin/install.php).Affected if The admin/install.php file is present on the server.
-
Check if install.php access is unrestrictedAttempt to access admin/install.php via HTTP without authentication or attempt to submit a request to it. Inspect server access logs for any successful requests to this endpoint.Affected if The install.php script can be accessed without authentication or was recently accessed by unauthorized users.
-
Inspect functions/db_connect.php for injected codeOpen functions/db_connect.php in a text editor or via command line and examine its contents. Look for base64_decode, eval, shell_exec, system, passthru, or other suspicious PHP functions, unusual encoded strings, or code that does not belong to the original application.Affected if The db_connect.php file contains obfuscated code, eval() calls, system command execution, or any PHP code that was not authored by the application developer.
-
Review web server logs for compromise indicatorsSearch web server access logs (e.g., Apache access.log, Nginx access.log) for POST requests to admin/install.php with unusual parameters, especially those containing PHP code patterns like '<?php', 'eval(', or 'base64'.
A user is affected if YVS Image Gallery is installed, admin/install.php exists and is accessible, and functions/db_connect.php contains injected PHP code or was recently modified.
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 dataRemove or restrict access to admin/install.php after completing installation, and follow all hardening recommendations in the product's installation documentation to prevent unauthenticated access to installation scripts.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5304 — 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-2012-5304 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