CVE-2012-1301
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 · uneditedThe FeedProxy.aspx script in Umbraco 4.7.0 allows remote attackers to proxy requests on their behalf via the "url" 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 · high confidenceThe FeedProxy.aspx script in Umbraco 4.7.0 contains an SSRF vulnerability where the 'url' parameter is not properly validated, allowing remote attackers to make the server fetch and return arbitrary URLs. This effectively turns the affected server into an open proxy, potentially enabling internal network reconnaissance, access to internal services, and cache poisoning attacks.
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= 4.7.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed Umbraco versionLocate the version file or check the About section in the Umbraco backend (typically at /umbraco/About.aspx) to find the exact version numberAffected if The installed version is exactly 4.7.0
-
Locate FeedProxy.aspx fileSearch the web root directory for FeedProxy.aspx - typically found in the root or /actions/ folder of the Umbraco installationAffected if The file FeedProxy.aspx exists on the server
-
Verify URL parameter acceptanceCheck if FeedProxy.aspx accepts a 'url' parameter by examining the page code or attempting a benign request (with proper authorization)Affected if The script accepts and processes a 'url' parameter without proper validation
You are affected if you are running Umbraco exactly version 4.7.0 and the FeedProxy.aspx file exists with its url parameter functional.
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.
dbcve · scopedUpgrade Umbraco to a patched version. If immediate patching is not feasible, remove or disable the FeedProxy.aspx file and implement WAF rules to block requests containing the 'url' parameter.
Umbraco CMS latest stable release (version 4.7.1 or later)
- Identify the current Umbraco installation version by checking the web.config file or dashboard
- Download the latest stable Umbraco CMS release from the official umbraco.com repository
- Before upgrading, perform a complete backup of the database and all files
- Review the Umbraco upgrade documentation for version-specific migration notes
- Test the upgrade in a staging environment before deploying to production
- Deploy the upgraded version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1301 — 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-1301 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