CVE-2018-15539
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 · uneditedAgentejo Cockpit lacks an anti-CSRF protection mechanism. Thus, an attacker is able to change API tokens, passwords, etc.
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 confidenceAgentejo Cockpit CMS lacks anti-CSRF protection mechanisms, allowing attackers to craft malicious requests that trick authenticated users into performing unintended actions such as changing passwords or API tokens.
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 dataall versionsCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 Agentejo Cockpit CMS installationLocate the main cockpit.php file or assets/config.php in the web root. Check for the directory structure containing /modules and /core folders typical of Cockpit CMS.Affected if The target system runs Agentejo Cockpit CMS
-
Check password change form for CSRF tokenLocate the password change functionality in the codebase (typically in /modules/Auth or similar). Inspect the HTML form or API endpoint that handles password changes. Look for a hidden input field or header containing a CSRF token value.Affected if No csrf_token, token, or similar hidden field is present in the password change form
-
Check API token modification for CSRF tokenLocate the API key/token management functionality (typically in /modules/Api or settings). Inspect the form or endpoint that creates or modifies API tokens. Look for a CSRF token field in the request.Affected if No csrf_token, token, or similar hidden field is present in the API token modification form
-
Verify CSRF token validation in request handlingSearch the PHP source code for the password change and API token endpoints. Look for validation logic that checks a token value against a stored session value (e.g., session_get, $session->token, $request->csrf).Affected if No server-side code validates a CSRF token before processing password or API token changes
-
Check Origin/Referer header validationInspect the application entry point or framework code for header validation. Look for checks on $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] that verify the request origin before allowing state-changing operations.Affected if No Origin or Referer header validation is performed on sensitive requests
The system is affected if it runs Agentejo Cockpit CMS and the password change and API token modification forms lack CSRF token fields and server-side validation.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations including password changes and API token modifications, along with proper Origin/Referer header validation.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15539 — 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-2018-15539 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