CVE-2013-4727
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 · uneditedDDSN Interactive cm3 Acora CMS 6.0.6/1a, 6.0.2/1a, 5.5.7/12b, 5.5.0/1b-p1, and possibly other versions, allows remote attackers to obtain sensitive information via a request to Admin/top.aspx.
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 confidenceThis is an information disclosure vulnerability in DDSN Interactive cm3 Acora CMS where the Admin/top.aspx page exposes sensitive information to unauthenticated remote attackers. The vulnerability affects multiple versions including 6.0.6/1a, 6.0.2/1a, 5.5.7/12b, and 5.5.0/1b-p1.
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= 5.5.0\/1b-p1= 5.5.7\/12b= 6.0.2\/1a= 6.0.6\/1aCVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 Acora CMS installationIdentify if DDSN Interactive cm3 Acora CMS is installed on the server by checking for the application in IIS, web server directories, or common installation paths such as /Inetpub/wwwroot/ or /var/www/. Look for directories named 'AcoraCMS' or 'cm3' and files with .aspx extensions typical of ASP.NET applications.Affected if Acora CMS software is present on the server and matches the affected version range.
-
Determine installed versionLocate version information in the installation directory, typically found in a config file, readme, or assembly metadata within the Acora CMS bin folder. Check files like version.txt, assemblyinfo.aspx, or the DLL file properties in the /bin directory.Affected if The installed version equals 5.5.0/1b-p1, 5.5.7/12b, 6.0.2/1a, or 6.0.6/1a.
-
Test Admin/top.aspx accessibilityUsing a web browser or command-line tool such as curl, attempt to access the URL path /Admin/top.aspx on the server without providing any authentication credentials. For example: http://target.example.com/Admin/top.aspxAffected if The page loads and returns HTTP 200 instead of redirecting to a login page or returning HTTP 401/403.
-
Verify sensitive information exposureExamine the response content from the Admin/top.aspx page to determine if it displays sensitive information such as server paths, configuration details, user credentials, database connection strings, or administrative data without requiring login.Affected if The page reveals sensitive system or configuration information to unauthenticated users.
A user is affected if Acora CMS versions 5.5.0/1b-p1, 5.5.7/12b, 6.0.2/1a, or 6.0.6/1a are installed and the /Admin/top.aspx endpoint is accessible without authentication, exposing sensitive information.
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 dataRestrict access to the Admin/top.aspx page through authentication or IP-based access controls. If the admin interface is not required, disable or remove the vulnerable endpoint entirely.
- 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-2013-4727 — 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-2013-4727 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