CVE-2013-4724
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 include the HTTPOnly flag in a Set-Cookie header for an unspecified cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.
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 confidenceDDSN Interactive cm3 Acora CMS fails to set the HTTPOnly flag on a cookie in its Set-Cookie header. This allows JavaScript in cross-site scripting (XSS) attacks to access the cookie value, potentially exposing session identifiers or other sensitive data that should be protected from client-side script access.
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 Acora CMS installed versionLocate the version identifier in the application administration panel, in a version file within the CMS installation directory, or by viewing the HTTP response headers from the application's login or main pageAffected if The installed version matches 5.5.0/1b-p1, 5.5.7/12b, 6.0.2/1a, or 6.0.6/1a
-
Capture Set-Cookie headers from the applicationLog into the Acora CMS application and capture HTTP responses using browser developer tools (Network tab), a proxy tool, or curl with -v flag to view response headersAffected if Set-Cookie headers are present in the response without the HttpOnly attribute
-
Inspect cookies for HttpOnly flagExamine each Set-Cookie header value and verify whether the string 'HttpOnly' appears in the cookie definitionAffected if Any session or authentication cookie is set without the HttpOnly flag, meaning the cookie can be accessed via JavaScript
-
Test cookie accessibility via JavaScriptIf the application has any reflected XSS input points, use browser console to run document.cookie and verify whether session cookies are exposed to client-side scriptAffected if Sensitive cookies such as session identifiers are visible through document.cookie
A user is affected if they are running one of the listed Acora CMS versions and their application's cookies lack the HttpOnly attribute in Set-Cookie headers, allowing XSS to steal cookie data.
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 dataModify the application code that sets the cookie to include the HTTPOnly attribute in the Set-Cookie header, or configure the web server to add this flag for the affected cookie.
- 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-4724 — 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-4724 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