ADR-004 - Security System Architecture
ADR-004: Security System Architecture
Section titled “ADR-004: Security System Architecture”Comprehensive security architecture for XOOPS CMS protecting against modern threats.
Status
Section titled “Status”Accepted - Core security layer since XOOPS 2.5
Context
Section titled “Context”Problem Statement
Section titled “Problem Statement”XOOPS needs a robust security system that:
- Protects against common web vulnerabilities (OWASP Top 10)
- Provides granular permission control across modules
- Enables secure user authentication with modern standards
- Prevents data breaches and unauthorized access
- Supports multi-level access control (admin, moderator, user, guest)
- Integrates with all modules seamlessly
Current Threats
Section titled “Current Threats”Modern web attacks include:
- SQL Injection - Malicious SQL in user input
- XSS (Cross-Site Scripting) - Injected JavaScript in pages
- CSRF (Cross-Site Request Forgery) - Unauthorized form submissions
- Authentication bypass - Weak session/password handling
- Authorization bypass - Privilege escalation
- Data exposure - Sensitive data in URLs, logs, or caches
XOOPS Security Requirements
Section titled “XOOPS Security Requirements”- User authentication and session management
- Role-based access control (RBAC)
- Permission system for modules and objects
- Input validation and output escaping
- Protection against common attacks
- Audit logging of security events
- Secure password handling
- CSRF token protection
Decision
Section titled “Decision”Core Security Architecture
Section titled “Core Security Architecture”graph TB subgraph "Authentication Layer" A["User Authentication<br/>(Login/Sessions)"] B["Session Management<br/>(Tokens/Cookies)"] C["Password Security<br/>(Hashing/Salts)"] end
subgraph "Authorization Layer" D["Role Management<br/>(Admin/User/Guest)"] E["Permission System<br/>(Module-level)"] F["Object Permissions<br/>(Item-level)"] end
subgraph "Protection Layer" G["Input Validation<br/>(Type/Format)"] H["Output Escaping<br/>(HTML/JavaScript)"] I["CSRF Protection<br/>(Token Validation)"] end
subgraph "Monitoring Layer" J["Audit Logging<br/>(Security Events)"] K["Rate Limiting<br/>(Brute Force)"] L["Intrusion Detection<br/>(Suspicious Activity)"] end
A --> B A --> C D --> E E --> F G --> I H --> I J --> K K --> LSecurity Components
Section titled “Security Components”1. Authentication System
Section titled “1. Authentication System”User Login Process:
<?php// 1. Validate credentials$user = $userHandler->findByLogin($username);if (!$user || !password_verify($password, $user->getVar('pass'))) { throw new AuthenticationException('Invalid credentials');}
// 2. Check if account is activeif (!$user->getVar('uactive')) { throw new AuthenticationException('Account inactive');}
// 3. Create secure sessionsession_regenerate_id(true);$_SESSION['uid'] = $user->getVar('uid');$_SESSION['token'] = bin2hex(random_bytes(32));$_SESSION['created'] = time();
// 4. Log the login$this->auditLog('USER_LOGIN', $user->getVar('uid'));Password Security:
<?php// Use password_hash (not MD5 or SHA1)$hashed = password_hash($password, PASSWORD_BCRYPT, [ 'cost' => 12, // High cost = slow brute force]);
// Verify passwordif (!password_verify($inputPassword, $hashed)) { throw new Exception('Invalid password');}
// Rehash if algorithm or cost changedif (password_needs_rehash($hashed, PASSWORD_BCRYPT, ['cost' => 12])) { $newHash = password_hash($password, PASSWORD_BCRYPT, ['cost' => 12]); $user->setVar('pass', $newHash); $userHandler->insert($user);}2. Session Management
Section titled “2. Session Management”Secure Session Handling:
<?php// Session configurationini_set('session.cookie_httponly', true); // No JS accessini_set('session.cookie_secure', true); // HTTPS onlyini_set('session.cookie_samesite', 'Strict'); // CSRF protectionini_set('session.gc_maxlifetime', 3600); // 1 hour timeoutini_set('session.sid_length', 64); // 64-char session ID
// Validate sessionfunction validateSession() { // Check timeout if (time() - $_SESSION['created'] > 3600) { session_destroy(); throw new SessionExpiredException(); }
// Validate user agent (prevent session hijacking) if ($_SESSION['user_agent'] !== $_SERVER['HTTP_USER_AGENT']) { throw new SessionInvalidException(); }
// Validate IP (optional, can be too strict) if (!in_array($_SERVER['REMOTE_ADDR'], $_SESSION['ips'])) { $_SESSION['ips'][] = $_SERVER['REMOTE_ADDR']; }}3. Authorization (RBAC)
Section titled “3. Authorization (RBAC)”Role-Based Access Control:
<?phpclass XoopsUser { public function hasPermission(string $permissionName): bool { // Get user groups $groups = $this->getGroups();
// Check if any group has permission foreach ($groups as $groupId) { if ($this->checkGroupPermission($groupId, $permissionName)) { return true; } }
return false; }
/** * User groups and their permissions * Admin: Full access * Moderator: Content management * User: Create own content * Guest: Read-only access */ private function checkGroupPermission(int $groupId, string $permission): bool { $permissions = [ 1 => ['admin_access'], // Admin group 2 => ['moderate_content', 'edit_own'], // Moderator group 3 => ['create_content', 'edit_own'], // User group 4 => [], // Guest group (no permissions) ];
return in_array($permission, $permissions[$groupId] ?? []); }}4. Input Validation
Section titled “4. Input Validation”Prevent SQL Injection and Type Errors:
<?php// Always use prepared statements$sql = 'SELECT * FROM users WHERE id = ?';$result = $db->query($sql, [$userId]); // ✅ Safe
// Input validationfunction validateUserInput(array $data): array{ return [ 'email' => filter_var($data['email'] ?? '', FILTER_VALIDATE_EMAIL), 'age' => filter_var($data['age'] ?? 0, FILTER_VALIDATE_INT), 'website' => filter_var($data['website'] ?? '', FILTER_VALIDATE_URL), 'title' => substr(trim($data['title'] ?? ''), 0, 255), ];}
// XOOPS Safe Input class$safe = \Xmf\Request::getHtmlRequest('var_name', '');$int = \Xmf\Request::getInt('page', 1);5. Output Escaping
Section titled “5. Output Escaping”Prevent XSS Attacks:
<?php// In PHP templatesecho htmlspecialchars($userInput, ENT_QUOTES, 'UTF-8');
// In Smarty templates (automatic escaping)<{$user_input}> {* Escaped by default *}<{$html|escape:false}> {* Only when needed *}
// JavaScript context<script>var message = "<{$userMessage|escape:'javascript'}>";</script>
// URL context<a href="<{$url|escape:'url'}>">Link</a>6. CSRF Protection
Section titled “6. CSRF Protection”Cross-Site Request Forgery Prevention:
<?php// Generate CSRF tokensession_start();if (empty($_SESSION['csrf_token'])) { $_SESSION['csrf_token'] = bin2hex(random_bytes(32));}
// In forms<form method="POST"> <input type="hidden" name="csrf_token" value="<{$csrf_token}>"> <button type="submit">Submit</button></form>
// Validate tokenif ($_SERVER['REQUEST_METHOD'] === 'POST') { if (hash_equals($_SESSION['csrf_token'], $_POST['csrf_token'] ?? '')) { // Process form } else { throw new InvalidTokenException('CSRF token invalid'); }}Consequences
Section titled “Consequences”Positive Effects
Section titled “Positive Effects”- Comprehensive Protection - Covers major vulnerability classes
- Layered Security - Multiple layers of defense
- Flexible RBAC - Fine-grained permission control
- Audit Trail - Track security events
- Industry Standard - Aligns with OWASP recommendations
- Module Integration - Easy for modules to use security APIs
Negative Effects
Section titled “Negative Effects”- Complexity - More code and configuration needed
- Performance - Hashing and validation add overhead
- User Experience - Security sometimes inconvenient
- Maintenance - Requires ongoing security updates
- Training Required - Developers must follow practices
Risks and Mitigations
Section titled “Risks and Mitigations”| Risk | Severity | Mitigation |
|---|---|---|
| Developer ignores security | High | Code review, security training |
| New vulnerabilities discovered | Medium | Regular security audits, updates |
| Performance impact | Low | Optimize hot paths, caching |
| Overly complex permissions | Medium | Clear documentation, examples |
Security Best Practices
Section titled “Security Best Practices”For Module Developers
Section titled “For Module Developers”<?php// ✅ DO: Use prepared statements$result = $db->prepare('SELECT * FROM table WHERE id = ?')->execute([$id]);
// ❌ DON'T: Concatenate queries$result = $db->query("SELECT * FROM table WHERE id = $id");
// ✅ DO: Escape outputecho htmlspecialchars($user_input, ENT_QUOTES, 'UTF-8');
// ❌ DON'T: Output raw user dataecho $user_input;
// ✅ DO: Check permissionsif (!$user->hasPermission('edit_content')) { throw new PermissionException();}
// ❌ DON'T: Trust user roles directlyif ($_POST['is_admin']) { // Make user admin - SECURITY HOLE!}
// ✅ DO: Validate input types$page = (int)$_GET['page'];
// ❌ DON'T: Use untrusted values directly$sql .= " LIMIT " . $_GET['limit'];Alternatives Considered
Section titled “Alternatives Considered”OAuth/OpenID Connect
Section titled “OAuth/OpenID Connect”Why not chosen initially: Too complex for shared hosting environment, but good for future integration with external auth systems.
Two-Factor Authentication (2FA)
Section titled “Two-Factor Authentication (2FA)”Status: Accepted as extension, not core requirement, see ADR-006
HTTP-only Session Cookies
Section titled “HTTP-only Session Cookies”Status: Implemented - prevents JavaScript access to session data
Related Decisions
Section titled “Related Decisions”- ADR-001: Modular Architecture - Modules implement security
- ADR-005: Module Permission System
- ADR-006: Two-Factor Authentication (future)
References
Section titled “References”Security Standards
Section titled “Security Standards”PHP Security
Section titled “PHP Security”Implementation Checklist
Section titled “Implementation Checklist”- User authentication system
- Session management
- Password hashing (bcrypt)
- Role-based access control
- Module permissions
- Input validation framework
- Output escaping (PHP + Smarty)
- CSRF token protection
- Security audit logging
- Rate limiting
- Security headers
Version History
Section titled “Version History”| Version | Date | Changes |
|---|---|---|
| 1.0.0 | 2024-01-28 | Initial document |
#xoops #adr #security #architecture #authentication #authorization #rbac