📄 Description (English)
A vulnerability was detected in TaleLin lin-cms-spring-boot up to 0.2.1. This issue affects some unknown processing of the file src/main/java/io/github/talelin/latticy/controller/v1/BookController.java of the component book Endpoint. The manipulation results in improper access controls. The attack may be launched remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
🤖 AI Executive Summary
CVE-2026-10152 is a medium-severity improper access control vulnerability in TaleLin lin-cms-spring-boot up to version 0.2.1 affecting the BookController endpoint. The vulnerability allows remote attackers to bypass access controls through manipulation of the book endpoint processing logic. With public exploit information available and no patch currently released, this poses an immediate risk to organizations using affected versions.
📄 Description (Arabic)
🤖 AI Intelligence Analysis Analyzed: May 31, 2026 02:16
🇸🇦 Saudi Arabia Impact Assessment
This vulnerability primarily impacts Saudi organizations using TaleLin lin-cms-spring-boot for content management systems, particularly in government digital transformation initiatives, educational institutions managing digital libraries, and media/publishing organizations. Government agencies (NCA oversight), universities, and digital content platforms are at highest risk. The improper access control could lead to unauthorized data access, modification of book records, or lateral movement within systems. Banking and financial sectors using this CMS for customer-facing portals face elevated risk of data breach and regulatory non-compliance with SAMA requirements.
🏢 Affected Saudi Sectors
Government and Public Administration
Education and Universities
Media and Publishing
Banking and Financial Services
Healthcare
Telecommunications
🎯 MITRE ATT&CK Techniques
⚖️ Saudi Risk Score (AI)
6.8
/ 10.0
🔧 Remediation Steps (English)
IMMEDIATE ACTIONS:
1. Identify all systems running TaleLin lin-cms-spring-boot versions up to 0.2.1 across your infrastructure
2. Isolate or restrict network access to affected BookController endpoints immediately
3. Enable enhanced logging and monitoring on book-related API endpoints
4. Review access logs for suspicious activity targeting /book endpoints
PATCHING GUIDANCE:
1. Monitor the official TaleLin GitHub repository for security patches
2. Prepare upgrade path to version 0.2.2 or later once available
3. Test patches in non-production environments before deployment
COMPENSATING CONTROLS (until patch available):
1. Implement Web Application Firewall (WAF) rules to restrict BookController access to authorized users only
2. Deploy API gateway authentication requiring valid credentials for all /book endpoints
3. Implement role-based access control (RBAC) at application level
4. Use network segmentation to limit access to CMS systems
5. Implement rate limiting on book endpoints to prevent automated exploitation
DETECTION RULES:
1. Monitor for unauthorized HTTP requests to /v1/book endpoints without proper authentication headers
2. Alert on access attempts from unexpected source IPs or user accounts
3. Track modifications to book records by unauthorized users
4. Monitor for privilege escalation attempts targeting book management functions
🔧 خطوات المعالجة (العربية)
الإجراءات الفورية:
1. تحديد جميع الأنظمة التي تقوم بتشغيل إصدارات TaleLin lin-cms-spring-boot حتى 0.2.1 عبر البنية التحتية الخاصة بك
2. عزل أو تقييد الوصول إلى نقاط نهاية BookController المتأثرة فوراً
3. تفعيل السجلات المحسنة والمراقبة على نقاط نهاية API المتعلقة بالكتب
4. مراجعة سجلات الوصول للنشاط المريب الموجه نحو نقاط نهاية /book
إرشادات التصحيح:
1. مراقبة مستودع TaleLin الرسمي على GitHub للحصول على تصحيحات الأمان
2. تحضير مسار الترقية إلى الإصدار 0.2.2 أو أحدث عند توفره
3. اختبار التصحيحات في بيئات غير الإنتاج قبل النشر
عناصر التحكم التعويضية (حتى توفر التصحيح):
1. تنفيذ قواعد جدار حماية تطبيقات الويب (WAF) لتقييد وصول BookController للمستخدمين المصرح لهم فقط
2. نشر بوابة API تتطلب بيانات اعتماد صحيحة لجميع نقاط نهاية /book
3. تنفيذ التحكم في الوصول القائم على الأدوار (RBAC) على مستوى التطبيق
4. استخدام تقسيم الشبكة لتحديد الوصول إلى أنظمة CMS
5. تنفيذ تحديد معدل على نقاط نهاية الكتب لمنع الاستغلال الآلي
قواعد الكشف:
1. مراقبة طلبات HTTP غير المصرح بها إلى نقاط نهاية /v1/book بدون رؤوس مصادقة صحيحة
2. التنبيه على محاولات الوصول من عناوين IP أو حسابات مستخدمين غير متوقعة
3. تتبع التعديلات على سجلات الكتب من قبل مستخدمين غير مصرح لهم
4. مراقبة محاولات تصعيد الامتيازات الموجهة نحو وظائف إدارة الكتب
📋 Regulatory Compliance Mapping
🟢 NCA ECC 2024
ECC 2024 A.9.1.1 - Access control policy and procedures
ECC 2024 A.9.2.1 - User registration and access rights management
ECC 2024 A.9.4.3 - Password management system
ECC 2024 A.14.2.1 - Secure development policy
🔵 SAMA CSF
SAMA CSF ID.AC-1 - Access Control Policy
SAMA CSF PR.AC-1 - Processes and procedures for access management
SAMA CSF PR.AC-3 - Access enforcement through role-based controls
SAMA CSF DE.CM-1 - Detection and monitoring of unauthorized access
🟡 ISO 27001:2022
ISO 27001:2022 A.5.3 - Segregation of duties
ISO 27001:2022 A.8.2 - User access management
ISO 27001:2022 A.8.3 - User responsibilities
ISO 27001:2022 A.9.2 - User access provisioning
ISO 27001:2022 A.9.4 - Access rights review
🟣 PCI DSS v4.0.1
PCI DSS 7.1 - Limit access to system components by business need to know
PCI DSS 7.2 - Establish an access control system for IT assets
🔗 References & Sources 5