dbcve.org
Maxsite CmsApplication · Maxsite

CVE-2023-36291

MEDIUM · 6.1 CVSS v3.1 Published 2023-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross Site Scripting vulnerability in Maxsite CMS v.108.7 allows a remote attacker to execute arbitrary code via the f_content parameter in the admin/page_new file.

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 confidence

Stored XSS vulnerability in Maxsite CMS v.108.7 allows injection of arbitrary JavaScript via the f_content parameter in the admin/page_new functionality. The application fails to properly sanitize user-supplied content before storage, causing the malicious payload to execute when the content is rendered in subsequent page views.

MitigationImplement proper input validation and output encoding for the f_content parameter using context-aware sanitization (HTML escaping, allowlisting safe HTML tags, or using a mature sanitization library). Apply the sanitization both at input time and when rendering content.

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
Maxsite CmsApplication
Affected:= 108.7

CVSS 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Maxsite CMS version
    Locate the version information file or admin panel about page to determine the installed Maxsite CMS version. Common locations include a version.php file, admin dashboard, or footer of admin pages.
    Affected if Installed version is exactly 108.7 (the '=' indicates this specific version only)
  2. Confirm admin access exists
    Check if the administrative interface is accessible. This may require valid admin credentials.
    Affected if Admin panel is accessible and functional
  3. Identify page_new functionality
    Locate the admin/page_new component in the application structure. This is the component that handles creating new pages in the CMS.
    Affected if The page_new functionality exists in the installation
  4. Examine f_content parameter handling
    Review how the f_content parameter is processed when creating new pages via the admin/page_new function. Look for sanitization routines in the relevant PHP file.
    Affected if The f_content parameter accepts user input without proper sanitization before storage
  5. Verify content storage mechanism
    Check if user-supplied content from f_content is stored in a database or file without validation.
    Affected if Content is stored without sanitization and can be retrieved later for display

Your environment is affected only if you have Maxsite CMS version 108.7 installed AND the admin/page_new functionality with the f_content parameter is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the f_content parameter using context-aware sanitization (HTML escaping, allowlisting safe HTML tags, or using a mature sanitization library). Apply the sanitization both at input time and when rendering content.

Recommended fix Moderate confidence

Latest stable Maxsite CMS version (108.8 or later) from github.com/maxsite/cms

  1. 1. Back up your entire Maxsite CMS installation, including the database, before proceeding with any updates.
  2. 2. Download the latest stable version of Maxsite CMS from the official repository at github.com/maxsite/cms
  3. 3. Review the release notes/changelog for version 108.8 or later to confirm the XSS vulnerability in the f_content parameter has been addressed.
  4. 4. Replace the core Maxsite CMS files with the new version files, preserving your custom configuration and content files.
  5. 5. Clear any cached data within the application.
  6. 6. Test the admin/page_new functionality to ensure the f_content parameter is now properly sanitized.
  7. 7. Verify that non-administrative users cannot inject malicious scripts through input fields.
Caveat Review release notes - minor CMS upgrades typically preserve configuration but major version jumps may require migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Maxsite Cms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36291 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36291 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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