Skip to content
KitploitKITPLOIT
도구블로그
제출
도구블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

··피드·문의·개인정보·© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
CVE-2026-48908-by-yora — Passive security checker for CVE-2026-48908 affecting SP Page Builder. | Kitploit
도구/GitHubGitHub/yora1928/cve-2026-48908-by-yora
ReconnaissanceVulnerability ScannersWeb Vulnerability ScannersPayload GenerationExploitationWeb Application ExploitationInformation GatheringWeb SecurityPenetration TestingRed Teaming
GitHubyora1928/cve-2026-48908-by-yora
2420일 전아직 검토되지 않음

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →
공유

CVE-2026-48908-by-yora

Passive security checker for CVE-2026-48908 affecting SP Page Builder.

저장소 보기
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

🔐 CVE-2026-48908 Scanner & Safe PoC

Joomla SP Page Builder — Unauthenticated File Upload / Potential RCE

Python License Joomla

Developed by yora


📌 About

This project is a security research and vulnerability detection tool developed by yora to help identify CVE-2026-48908 affecting SP Page Builder for Joomla.

The vulnerability is related to an unauthenticated file upload mechanism. Under vulnerable conditions, an attacker may be able to upload an unexpected file type, potentially leading to Remote Code Execution (RCE).

⚠️ Important: Use this project only against systems you own or systems for which you have explicit authorization to perform security testing.

Affected Versions

  • Affected: SP Page Builder 1.0.0 through 6.6.1
  • Fixed: SP Page Builder 6.6.2 and later

👨‍💻 Developer

yora

  • GitHub: https://github.com/yora1928
  • Project: https://github.com/yora1928/CVE-2026-48908-by-yora

✨ Features

The public documentation intentionally does not provide a weaponized shell, command-execution URL, or instructions for obtaining unauthorized access.


🚀 Installation

Clone Repository

root@kitploit:~
git clone https://github.com/yora1928/CVE-2026-48908-by-yora.git
cd CVE-2026-48908-by-yora

Install Dependencies

root@kitploit:~
python -m pip install -r requirements.txt

requirements.txt

root@kitploit:~
requests>=2.28.0

📖 Usage

1. Detection Only

Use the scanner in detection mode against an authorized target:

root@kitploit:~
python scanner.py --url https://your-authorized-target.example

Example result:

root@kitploit:~
[CONFIRMED] https://your-authorized-target.example
    ├─ SP Page Builder detected
    ├─ Version: 6.3.1
    └─ Vulnerable version and relevant endpoint exposure detected

2. Authorized Validation / PoC

The project can be used for controlled validation in a laboratory or authorized environment.

The purpose of validation is to establish whether the vulnerable upload behavior is present without turning the documentation into a ready-to-use remote shell.

root@kitploit:~
python scanner.py --url https://your-authorized-target.example --exploit

For safe research, use an isolated test environment and inspect the generated evidence and report rather than attempting to access systems without authorization.


3. Scan Multiple Authorized Targets

Create targets.txt:

root@kitploit:~
https://site1.example
https://site2.example

Run:

root@kitploit:~
python scanner.py --list targets.txt --threads 5

Only include systems that you are authorized to test.


4. Save Results as JSON

root@kitploit:~
python scanner.py --url https://your-authorized-target.example --output reports/result.json

5. Cleanup

After authorized testing, review the generated evidence and remove any test artifacts from the target.

root@kitploit:~
python scanner.py --url https://your-authorized-target.example --exploit --cleanup

If the tool reports an artifact location, verify it against your test environment and remove it using your normal authorized administration method.


📊 Result Classification


📁 JSON Report Example

A scan report may contain information similar to:

root@kitploit:~
{
  "scanner": "CVE-2026-48908 Scanner",
  "scan_time": "2026-08-13T10:30:00+00:00",
  "total_targets": 1,
  "results": [
    {
      "target": "https://authorized-target.example",
      "classification": {
        "status": "CONFIRMED",
        "confidence": "high",
        "reasoning": [
          "Vulnerable SP Page Builder version detected",
          "Relevant upload endpoint exposure confirmed"
        ]
      },
      "validation": {
        "upload_behavior_confirmed": true,
        "test_artifacts_reviewed": true
      }
    }
  ]
}

📁 Project Structure

root@kitploit:~
CVE-2026-48908-by-yora/
├── scanner.py          # Main detection and validation tool
├── requirements.txt    # Python dependencies
├── README.md           # Project documentation
├── SECURITY.md         # Security policy and reporting
├── LICENSE             # MIT License
├── detection/          # Optional detection modules
├── poc/                # Optional proof-of-concept modules
└── reports/            # JSON scan reports

🔎 Vulnerability Overview

What is CVE-2026-48908?

CVE-2026-48908 affects SP Page Builder for Joomla and is associated with an unauthenticated file upload vulnerability.

The security issue is significant because an unrestricted or insufficiently validated upload mechanism can allow an attacker to place an executable file on a server.

If the uploaded file is interpreted by the server, the vulnerability may lead to:

Unauthenticated File Upload → Server-Side File Placement → Potential Code Execution → Possible Server Compromise


💥 Potential Impact

A vulnerable installation may face risks including:

  • Unauthorized file uploads
  • Remote Code Execution
  • Server compromise
  • Unauthorized modification of application files
  • Potential exposure of application data
  • Website defacement
  • Loss of confidentiality, integrity, or availability

The actual impact depends on the server configuration, permissions, PHP environment, Joomla configuration, and other security controls.


🛡️ Mitigation

If you are running an affected version:

  1. Upgrade SP Page Builder to 6.6.2 or later.
  2. Review the server for unexpected uploaded files.
  3. Review web server and application logs for suspicious requests.
  4. Check Joomla extensions and components for unexpected changes.
  5. Rotate credentials if compromise is suspected.
  6. Continue monitoring the server after remediation.

🔒 Responsible Use

This project is intended for:

  • Security research
  • Vulnerability validation
  • Authorized penetration testing
  • Education
  • Defensive security assessment
  • Testing in isolated laboratories

Do not use this project to:

  • Scan random internet targets without permission
  • Upload files to systems you do not control
  • Obtain unauthorized access
  • Maintain persistence on compromised systems
  • Collect credentials or private information
  • Disrupt services

Authorization matters. Always obtain permission before testing a system that you do not own.


📬 Contributions & Security Reports

If you find a bug in this project or want to contribute:

  • Open an Issue
  • Submit a Pull Request
  • Follow the security reporting procedure in SECURITY.md

Please avoid publishing sensitive information or working exploit details in public issues.


📜 License

This project is released under the MIT License.

See LICENSE for the full license text.


🙏 Credits

Research and implementation:

yora1928

Project repository:

https://github.com/yora1928/CVE-2026-48908-by-yora


🔐 Security Research by yora1928

Learn • Research • Report • Secure

도구 다운로드
FeatureDescription
🔍 Component DetectionDetects Joomla and SP Page Builder from available application indicators.
📌 Version FingerprintingAttempts to identify the installed SP Page Builder version.
🧪 Endpoint ValidationChecks whether the relevant upload functionality is exposed without the expected authentication.
📊 ClassificationClassifies results as CONFIRMED, LIKELY, NOT_VULNERABLE, UNKNOWN, or ERROR.
📁 JSON ReportsSaves scan evidence and classification results in JSON format.
⚡ Multi-threadingSupports scanning authorized target lists with configurable threads.
🧹 Cleanup GuidanceProvides information for reviewing and removing test artifacts created during authorized testing.
StatusMeaningRecommended Action
🔴 CONFIRMEDSP Page Builder was detected, a vulnerable version was identified, and relevant endpoint exposure was confirmed.Upgrade to 6.6.2 or later and review the system for suspicious artifacts.
🟡 LIKELYA vulnerable version was detected, but endpoint behavior could not be fully confirmed.Perform additional validation in an authorized environment.
🟢 NOT_VULNERABLESP Page Builder 6.6.2+ was detected.Keep the extension updated and continue normal security monitoring.
⚪ UNKNOWNThe component/version could not be identified reliably.Verify the installed extension and version manually.
❌ ERRORThe scanner encountered a connection, timeout, or other technical error.Check connectivity, firewall rules, and scanner configuration.