CVE-2023-29009
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 · uneditedbaserCMS is a website development framework with WebAPI that runs on PHP8 and CakePHP4. There is a XSS Vulnerability in Favorites Feature to baserCMS. This issue has been patched in version 4.8.0.
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 confidencebaserCMS versions prior to 4.8.0 contain a Cross-Site Scripting (XSS) vulnerability in the Favorites feature. The vulnerability allows attackers to inject malicious scripts through the favorites functionality, potentially compromising user sessions or displaying malicious content to other users.
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< 4.8.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed basercms versionLocate the version file or admin panel version display. In baserCMS, check the version via the admin dashboard (typically /admin) or look for a version.php file in the installation root.Affected if The installed version is less than 4.8.0 (e.g., 4.7.x, 4.6.x, or earlier)
-
Verify Favorites feature accessibilityLog into the baserCMS admin panel and navigate to the Favorites section, typically found in the user settings or dashboard area. Alternatively, check if the /baser/api/favorites endpoint is accessible via API tools.Affected if The Favorites feature exists and is accessible to users (the vulnerability exists in this feature regardless of whether it has been actively used)
-
Examine existing favorites entriesQuery the favorites table in the baserCMS database (commonly named baser_favorites or similar) or view favorites through the admin panel interface. Look for any entries containing HTML script tags, javascript: URIs, or other suspicious script content.Affected if Any favorites contain encoded or raw script tags, event handlers (onclick, onerror, etc.), or other XSS payload patterns
-
Review access logs for favorites-related requestsExamine web server access logs (Apache/nginx) and baserCMS application logs for POST requests to favorites endpoints containing unusual characters or patterns typical of XSS attempts.Affected if Log entries show malicious script content submitted through favorites functionality
You are affected if your basercMS version is below 4.8.0 and the Favorites feature is accessible in your environment.
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.
dbcve · scoped4.8.0
Upgrade baserCMS to version 4.8.0 or later, which contains the patch for this XSS vulnerability in the Favorites feature.
4.8.0
- 1. Back up your current baserCMS installation and database
- 2. Download baserCMS version 4.8.0 from the official basercms.net website or GitHub repository
- 3. Upload and extract the new files to your server, replacing the existing installation
- 4. Run any available database migration scripts included in the 4.8.0 release
- 5. Clear any cache files to ensure the new version loads correctly
- 6. Verify the Favorites feature works correctly and test for XSS vulnerability resolution
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-29009 — 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-2023-29009 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