CVE-2013-4725
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, does not set the secure flag for an unspecified cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.
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 DDSN Interactive cm3 Acora CMS fails to set the Secure flag on cookies during HTTPS sessions. This allows cookies to potentially be transmitted over unencrypted connections, enabling attackers on the same network to intercept and capture session cookies via man-in-the-middle 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= 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.
-
Identify the installed Acora CMS versionLocate the version identifier in the application installation directory, admin panel, or application metadata files. Common locations include a version file, about page, or configuration files within the cm3 installation directory.Affected if The installed version matches 5.5.0/1b-p1, 5.5.7/12b, 6.0.2/1a, or 6.0.6/1a exactly.
-
Confirm HTTPS is enabled for the applicationVerify that the web server or application is configured to serve content over HTTPS. Check the web server configuration or access the application via an https:// URL.Affected if HTTPS is active and the application serves content over encrypted connections.
-
Inspect Set-Cookie response headersUsing browser developer tools, a proxy, or command-line tools like curl with -I flag, make an HTTPS request to the application and examine the Set-Cookie headers in the response. Look for the presence or absence of the Secure attribute.Affected if Cookies are set during HTTPS sessions but do NOT include the Secure flag in the Set-Cookie header.
-
Verify cookie transmission over non-HTTPSIf accessible, attempt an HTTP request to the application and observe whether session cookies are transmitted in cleartext.Affected if Session cookies are transmitted over unencrypted HTTP connections.
You are affected if you are running any of the specific versions 5.5.0/1b-p1, 5.5.7/12b, 6.0.2/1a, or 6.0.6/1a of Acora CMS with HTTPS enabled but without the Secure flag on session cookies.
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 dataConfigure the application to set the Secure flag on all session cookies, ensuring they are only transmitted over encrypted HTTPS connections. This is typically done in the session or cookie configuration of the web application.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4725 — 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-4725 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