dbcve.org
InjectionWeakness · CWE-74

CVE-2026-13529

MEDIUM · 5.6 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in YzmCMS up to 7.5. This affects an unknown function of the file /application/install/index.php. Executing a manipulation of the argument siteurl can lead to sql injection. The attack can be executed remotely. A high complexity level is associated with this attack. The exploitability is reported as difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in YzmCMS up to version 7.5 in the /application/install/index.php file via manipulation of the 'siteurl' parameter. The attack can be exploited remotely but requires high complexity and difficult exploitability conditions.

MitigationRestrict web access to /application/install/ in production environments (via web server configuration or removal of install files), and upgrade to a patched version of YzmCMS when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm YzmCMS is installed
    Look for YzmCMS installation by checking for the presence of typical YzmCMS directory structure, such as /application/, /statics/, or /uploads/ directories in the web root. Also check for YzmCMS-specific files like index.php in the root that references 'YzmCMS'.
    Affected if The web application is running YzmCMS and the /application/ directory structure is present.
  2. Check YzmCMS version number
    Locate the version indicator in the YzmCMS installation. Check common locations such as a version.php file in the /application/ or /core/ directory, or look for a VERSION or version constant defined in core framework files. Compare the installed version to the affected range: version 7.5 and below are vulnerable.
    Affected if The installed YzmCMS version is 7.5 or lower.
  3. Verify the vulnerable file exists
    Check if the file /application/install/index.php exists in the web root. This is the file containing the SQL injection vulnerability in the 'siteurl' parameter.
    Affected if The file /application/install/index.php exists on the server.
  4. Check if installation has been completed
    Look for an install lock file that YzmCMS typically creates after installation completes, commonly named install.lock or similar, usually in the /application/install/ or /data/ directory. If the lock file exists, the install process has already run.
    Affected if The install lock file does NOT exist, meaning the installation may be re-runnable and the vulnerable code is accessible.
  5. Assess web access to install directory
    Determine if the /application/install/ directory is accessible via HTTP/HTTPS requests from the web. Attempt to access the URL or check web server configuration for any rewrite rules or access controls that explicitly allow or block this path.
    Affected if The /application/install/ directory is accessible over the web and not blocked by web server configuration.

A user is affected if YzmCMS version 7.5 or lower is installed, the /application/install/index.php file exists, and the install directory is web-accessible without being locked after installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict web access to /application/install/ in production environments (via web server configuration or removal of install files), and upgrade to a patched version of YzmCMS when available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13529 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13529 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data