CVE-2026-8739: Use of Hard-coded Cryptographic Key in Sanluan PublicCMS
A vulnerability was detected in Sanluan PublicCMS 5.202506.d. The affected element is the function getSignKey of the file publiccms-core/src/main/java/com/publiccms/logic/component/config/SafeConfigComponent.java. The manipulation of the argument privatefile_key results in use of hard-coded cryptographic key . The attack can be executed remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
AI Analysis
Technical Summary
Sanluan PublicCMS 5.202506.d contains a vulnerability in the getSignKey function located in publiccms-core/src/main/java/com/publiccms/logic/component/config/SafeConfigComponent.java. The issue arises from the use of a hard-coded cryptographic key (privatefile_key), which can be manipulated remotely. This weakens the cryptographic security of the application, potentially allowing attackers to bypass protections relying on this key. The vulnerability is remotely exploitable without authentication and has a CVSS 4.0 score of 6.9 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P). The vendor has not provided any patch or mitigation guidance, and the exploit is publicly available.
Potential Impact
The use of a hard-coded cryptographic key can allow attackers to compromise the confidentiality or integrity of data protected by this key. Since the vulnerability is remotely exploitable without privileges or user interaction, attackers could potentially perform unauthorized cryptographic operations or bypass security controls relying on the key. However, the impact is limited to the cryptographic component and does not directly indicate system-wide compromise. No known active exploitation in the wild has been reported.
Mitigation Recommendations
No official patch or remediation is currently available from the vendor. Users should monitor the vendor's channels for updates. In the meantime, consider mitigating risk by restricting network access to the affected service, applying compensating controls to protect sensitive data, or replacing the affected component if possible. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-8739: Use of Hard-coded Cryptographic Key in Sanluan PublicCMS
Description
A vulnerability was detected in Sanluan PublicCMS 5.202506.d. The affected element is the function getSignKey of the file publiccms-core/src/main/java/com/publiccms/logic/component/config/SafeConfigComponent.java. The manipulation of the argument privatefile_key results in use of hard-coded cryptographic key . The attack can be executed remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Sanluan PublicCMS 5.202506.d contains a vulnerability in the getSignKey function located in publiccms-core/src/main/java/com/publiccms/logic/component/config/SafeConfigComponent.java. The issue arises from the use of a hard-coded cryptographic key (privatefile_key), which can be manipulated remotely. This weakens the cryptographic security of the application, potentially allowing attackers to bypass protections relying on this key. The vulnerability is remotely exploitable without authentication and has a CVSS 4.0 score of 6.9 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P). The vendor has not provided any patch or mitigation guidance, and the exploit is publicly available.
Potential Impact
The use of a hard-coded cryptographic key can allow attackers to compromise the confidentiality or integrity of data protected by this key. Since the vulnerability is remotely exploitable without privileges or user interaction, attackers could potentially perform unauthorized cryptographic operations or bypass security controls relying on the key. However, the impact is limited to the cryptographic component and does not directly indicate system-wide compromise. No known active exploitation in the wild has been reported.
Mitigation Recommendations
No official patch or remediation is currently available from the vendor. Users should monitor the vendor's channels for updates. In the meantime, consider mitigating risk by restricting network access to the affected service, applying compensating controls to protect sensitive data, or replacing the affected component if possible. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-05-16T10:36:27.832Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a09770eec166c07b0ab1a23
Added to database: 5/17/2026, 8:06:38 AM
Last enriched: 5/17/2026, 8:21:36 AM
Last updated: 5/17/2026, 9:28:22 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.