CVE-2026-38930: OpenRapid RapidCMS v1.3.1 was discovered to contain an authentication bypass in the /template/default/menu....
OpenRapid 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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-38930 affects OpenRapid RapidCMS v1.3.1 and involves authentication bypass through SQL injection in the default menu component. An unauthenticated remote attacker may be able to manipulate a cookie value to access data or functions they should not reach. Public sources rate it medium severity, with limited confidentiality and integrity impact and no availability impact stated.
Executive priority
Treat this as a near-term web application risk if RapidCMS v1.3.1 is internet-facing. It is not currently supported by KEV evidence, but unauthenticated network reachability and authentication bypass make confirmation and remediation planning important.
Technical view
The issue is reported in /template/default/menu.php. The vulnerable input is the name cookie parameter, where crafted SQL input can cause an authentication bypass. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, score 6.5. The weakness is classified as CWE-89, SQL Injection.
Likely exposure
Exposure is likely limited to organizations running OpenRapid RapidCMS v1.3.1 with the default menu.php component reachable over the network. The CVE record’s affected-product metadata is incomplete, so teams should verify installed versions and deployment paths directly.
Exploitation context
The public description says the vulnerability is exploited through a crafted SQL payload in the name cookie parameter. No CISA KEV listing is provided, and the supplied sources do not establish active exploitation in the wild.
Researcher notes
The public record is sparse. It identifies RapidCMS v1.3.1, menu.php, the name cookie, CWE-89, and CVSS 6.5. It does not provide a confirmed patch level, broad affected-version range, or independent exploitation telemetry in the supplied sources.
Mitigation direction
Check OpenRapid RapidCMS vendor or maintainer guidance for patches or configuration changes.
Restrict public access to RapidCMS administrative or template paths where feasible.
Apply web application firewall filtering for suspicious SQL injection patterns in cookies.
Review application code handling the name cookie for parameterized database access.
Back up the CMS and database before applying any changes.
Validation and detection
Inventory RapidCMS deployments and confirm whether v1.3.1 is in use.
Confirm whether /template/default/menu.php is present and externally reachable.
Review web logs for suspicious name cookie values and authentication anomalies.
Verify whether vendor updates or advisories exist after the CVE publication date.
Perform defensive testing only in an authorized staging environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.