CVE-2025-50567: Saurus CMS Community Edition 4.7.1 contains a vulnerability in the custom DB::prepare() function, which use...
Saurus CMS Community Edition 4.7.1 contains a vulnerability in the custom DB::prepare() function, which uses preg_replace() with the deprecated /e (eval) modifier to interpolate SQL query parameters. This leads to injection of user-controlled SQL statements, potentially leading to arbitrary PHP code execution.
Security readout for executives and security teams
Plain-English summary
CVE-2025-50567 is a critical issue reported in Saurus CMS Community Edition 4.7.1. A flawed database preparation function may let unauthenticated attackers inject SQL and potentially reach arbitrary PHP code execution. For organizations running this CMS, this should be treated as urgent until vendor guidance or compensating controls are confirmed.
Executive priority
High priority for any organization using the affected CMS version, especially if internet-facing. The potential business impact includes data theft, site compromise, service disruption, and server takeover. If the product is not present, no action is needed beyond documenting non-exposure.
Technical view
The report describes unsafe use of preg_replace() with the deprecated /e eval modifier inside a custom DB::prepare() function. User-controlled query parameters may be evaluated during SQL interpolation, creating both SQL injection and PHP code execution risk. The CVSS 3.1 score is 10.0 with network, low-complexity, no-authentication characteristics.
Likely exposure
Exposure appears limited to environments running Saurus CMS Community Edition 4.7.1, based on the CVE description. The structured affected-product data is incomplete, listing vendor and product as n/a, so asset owners should verify CMS name and version from installed systems rather than relying only on CPE matching.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle. The sources do not state active exploitation in the wild. However, the reported attack characteristics are severe: remote, unauthenticated, low complexity, and potentially full confidentiality, integrity, and availability impact.
Researcher notes
Evidence is based on the CVE record and linked researcher write-up. The affected-product metadata is incomplete, and no official vendor fix is named in the supplied sources. Avoid assuming broader version impact without confirmation. Validate against the specific vulnerable function and deployment context.
Mitigation direction
Identify any Saurus CMS Community Edition 4.7.1 deployments.
Check official vendor or project guidance for a fixed release or advisory.
Restrict public access to affected CMS instances where business permits.
Increase monitoring around CMS requests, database errors, and PHP execution anomalies.
Prioritize replacement or isolation if no maintained fix is available.
Validation and detection
Confirm installed CMS product and exact version from asset inventory or administration records.
Review application code for the vulnerable custom DB::prepare() implementation.
Check whether any vendor patch or local code change removed preg_replace /e usage.
Review logs for unusual database errors or suspicious CMS request patterns.
Document exposure: internet-facing status, authentication boundaries, and compensating controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.