CVE-2012-4519
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 · uneditedZenphoto before 1.4.3.4 admin-news-articles.php date parameter XSS.
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 · high confidenceReflected cross-site scripting (XSS) vulnerability in Zenphoto CMS admin panel. The date parameter in admin-news-articles.php does not properly sanitize user-supplied input before including it in the HTTP response, allowing an authenticated attacker to inject malicious JavaScript.
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< 1.4.3.4CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm Zenphoto installation and versionLocate Zenphoto and check its version number. Common locations: root directory contains zp-config.php or a version.php file. Check the admin dashboard footer for the version display, or inspect the main Zenphoto version file (typically includes/version.php or similar).Affected if The installed Zenphoto version is lower than 1.4.3.4 (e.g., 1.4.3.3, 1.4.3, 1.4.2, etc.)
-
Verify admin panel access existsConfirm the Zenphoto admin directory exists and is accessible at /zp-admin/ or /zenphoto/zp-admin/ relative to the installation root. Attempt to access the login page.Affected if The Zenphoto admin panel is accessible and the attacker could potentially authenticate to reach the vulnerable page.
-
Locate the vulnerable scriptNavigate to the file admin-news-articles.php within the Zenphoto admin directory. Verify the file exists in the installation.Affected if The file admin-news-articles.php exists in the Zenphoto admin directory, indicating the news articles module is present.
-
Inspect the date parameter handlingAccess the admin-news-articles.php page in a browser or via request, then examine how the 'date' parameter is handled in the HTTP response. Look for unescaped or unsanitized inclusion of the date parameter value in the page output.Affected if The date parameter value is reflected back in the HTML response without proper output encoding or sanitization, allowing script injection.
A user is affected if they run Zenphoto versions prior to 1.4.3.4 with the admin panel accessible and the admin-news-articles.php file present, where the date parameter is not output-encoded.
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 data1.4.3.4
Upgrade Zenphoto to version 1.4.3.4 or later which contains the patch. Alternatively, apply output encoding/sanitization to the date parameter in admin-news-articles.php before reflecting user input.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4519 — 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-4519 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