CVE-2026-38930
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 · uneditedOpenRapid RapidCMS v1.3.1 was discovered to contain an authentication bypass in the /template/default/menu.php component. This vulnerability is exploited via injecting a crafted SQL payload into the name cookie parameter.
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 confidenceOpenRapid RapidCMS v1.3.1 contains an authentication bypass vulnerability in /template/default/menu.php. The vulnerability is exploited through SQL injection via the 'name' cookie parameter, allowing attackers to bypass authentication mechanisms and potentially gain unauthorized access to the CMS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 RapidCMS installation versionCheck for version file (typically version.php, CHANGELOG, or admin dashboard About page) or inspect source files for version strings like '1.3.1'Affected if Installed version is 1.3.1 or falls within the 1.x range prior to patch
-
Verify vulnerable file presenceLocate /template/default/menu.php in the web root directoryAffected if The file menu.php exists in /template/default/ path
-
Inspect authentication logic in menu.phpOpen menu.php and search for SQL queries that reference cookie parameters, specifically looking for 'name' cookie usage in authentication checksAffected if The code processes the 'name' cookie value in SQL queries without proper sanitization
-
Confirm cookie-based authentication is activeCheck CMS configuration or authentication settings to determine if cookie-based login (remember me or similar feature) is enabled, which would route through menu.phpAffected if Cookie-based authentication is enabled and menu.php handles the authentication flow
-
Test vulnerable parameter acceptanceSend a request to any RapidCMS page and inspect whether the 'name' cookie is accepted and processed by the applicationAffected if The application accepts and processes the 'name' cookie parameter in authentication logic
Environment is affected if RapidCMS version 1.3.1 is installed, the file /template/default/menu.php exists, and cookie-based authentication with the 'name' parameter is enabled.
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 proper input validation and sanitization for cookie parameters, and replace vulnerable SQL queries with parameterized queries or prepared statements to prevent SQL injection-based authentication bypass.
- Consultation4.0 h
- Implementation6.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38930 — 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-2026-38930 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