CVE-2025-64048
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 · uneditedYCCMS 3.4 contains a stored cross-site scripting (XSS) vulnerability in the article management functionality. The vulnerability exists in the add() and getPost() functions within the ArticleAction.class.php file due to improper neutralization of user input in the article title field.
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 confidenceYCCMS 3.4 contains a stored XSS vulnerability in the article management functionality. The add() and getPost() functions in ArticleAction.class.php fail to properly neutralize user input in the article title field, allowing stored malicious scripts to execute when other users view articles.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.4CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm YCCMS version is 3.4Locate the version file or header in the YCCMS installation directory. Check files like version.php, README, or the admin dashboard version display for the exact version number.Affected if The installed version is exactly 3.4 (the affected version)
-
Verify article management module is accessibleLog into the YCCMS admin panel and navigate to the article management section. Check if the add() function in ArticleAction.class.php is accessible via the web interface.Affected if The article management module is enabled and accessible to users
-
Identify articles in the systemUse the getPost() function or navigate to the article listing page to view all published articles. Examine the article titles displayed in the system.Affected if There are articles stored in the system with titles that could contain unsanitized user input
-
Inspect article titles for potential XSS payloadsView the HTML source of article listing pages and article detail pages. Look for article titles in the rendered HTML without proper encoding (e.g., unescaped <script> tags, event handlers, or javascript: URLs).Affected if Article titles are rendered without output encoding, allowing script execution
-
Check article input handlingSubmit a test article with a benign XSS probe in the title field (e.g., <script>alert(1)</script> or <img src=x onerror=alert(1)>). Submit and then view the article to see if the payload executes or appears literally in the HTML.Affected if The submitted script payload executes or appears unescaped when viewing the article
A user is affected if they are running YCCMS version 3.4 with the article management module enabled and article titles are rendered without proper output encoding.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement input validation and output encoding on the article title field in the affected functions to prevent script injection. Use context-appropriate encoding when displaying article titles.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64048 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64048 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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