CVE-2018-15848
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 · uneditedAn issue was discovered in portfolioCMS 1.0.5. There is CSRF to create new pages via admin/portfolio.php?newpage=true.
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 confidenceportfolioCMS 1.0.5 lacks anti-CSRF protection on the page creation functionality at admin/portfolio.php?newpage=true. An attacker can craft a malicious page that forces an authenticated administrator's browser to submit a request creating new pages without the administrator's consent.
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= 1.0.5CVSS 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 installed portfolioCMS versionLocate the version file or footer in the application. Check for a version.php, README, or the main index page footer that displays the software version.Affected if The installed version is exactly 1.0.5.
-
Verify admin/portfolio.php existsAccess the URL path /admin/portfolio.php?newpage=true in the application using a browser or curl request. Confirm the page loads and presents a page creation form.Affected if The page creation form at admin/portfolio.php?newpage=true is accessible and functional.
-
Inspect page creation form for CSRF tokenView the HTML source of admin/portfolio.php?newpage=true. Search for a hidden input field containing a token value (commonly named 'csrf_token', 'token', 'csrf', or 'nonce') or check if the form submission includes any token parameter.Affected if No hidden CSRF token field is found in the page creation form, meaning anti-CSRF protection is absent.
-
Check session cookie SameSite attributeLog in as administrator, open browser developer tools, go to the Application/Storage tab, and inspect the session cookie. Alternatively, use curl to retrieve headers and check the Set-Cookie header for the SameSite attribute.Affected if The session cookie lacks the SameSite attribute or has it set to None/Lax without other CSRF mitigations in place.
-
Check Origin/Referer header validationSubmit a page creation request using a tool like curl or Burp Repeater with a mismatched or missing Origin/Referer header. Observe whether the server rejects the request.Affected if The server accepts requests with arbitrary or missing Origin/Referer headers, indicating no server-side CSRF protection.
The environment is affected if portfolioCMS version 1.0.5 is running and the page creation form at admin/portfolio.php?newpage=true lacks CSRF tokens and server-side Origin/Referer 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 for all state-changing operations including page creation, validate Origin/Referer headers server-side, and consider setting SameSite attribute on session cookies.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15848 — 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-15848 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