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 within SafeConfigComponent.java where a hard-coded cryptographic key (privatefile_key) is used. This insecure practice can allow remote attackers to bypass cryptographic protections by exploiting the fixed key. The vulnerability is remotely exploitable without authentication or user interaction. The vendor was contacted but did not respond, and no patch or mitigation has been officially released. The CVSS 4.0 score is 6.9, indicating a medium severity vulnerability with partial impact on data integrity.
Potential Impact
The use of a hard-coded cryptographic key can undermine the confidentiality and integrity of cryptographic operations within the affected CMS, potentially allowing attackers to forge signatures or decrypt sensitive data protected by the key. The vulnerability is remotely exploitable without authentication, increasing the risk of unauthorized access or manipulation. However, the impact is limited to integrity and does not affect availability or confidentiality directly according to the CVSS vector. No known exploits in the wild have been reported to date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vendor has not responded and no official fix is available, users should consider mitigating risk by restricting network access to the affected service, monitoring for suspicious activity related to cryptographic operations, and preparing to apply any future patches promptly once released. Avoid relying on the affected version in sensitive environments until a fix is provided.
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.
CVSS v4.0
Score 6.9medium
Affected software
pkg:maven/com.publiccms/publiccmsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Sanluan PublicCMS 5.202506.d contains a vulnerability in the getSignKey function within SafeConfigComponent.java where a hard-coded cryptographic key (privatefile_key) is used. This insecure practice can allow remote attackers to bypass cryptographic protections by exploiting the fixed key. The vulnerability is remotely exploitable without authentication or user interaction. The vendor was contacted but did not respond, and no patch or mitigation has been officially released. The CVSS 4.0 score is 6.9, indicating a medium severity vulnerability with partial impact on data integrity.
Potential Impact
The use of a hard-coded cryptographic key can undermine the confidentiality and integrity of cryptographic operations within the affected CMS, potentially allowing attackers to forge signatures or decrypt sensitive data protected by the key. The vulnerability is remotely exploitable without authentication, increasing the risk of unauthorized access or manipulation. However, the impact is limited to integrity and does not affect availability or confidentiality directly according to the CVSS vector. No known exploits in the wild have been reported to date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since the vendor has not responded and no official fix is available, users should consider mitigating risk by restricting network access to the affected service, monitoring for suspicious activity related to cryptographic operations, and preparing to apply any future patches promptly once released. Avoid relying on the affected version in sensitive environments until a fix is provided.
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: 05/17/2026, 08:06:38 UTC
Last enriched: 05/24/2026, 19:27:46 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 88
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.