CVE-2023-1613
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 · uneditedA vulnerability has been found in Rebuild up to 3.2.3 and classified as problematic. This vulnerability affects unknown code of the file /feeds/post/publish. The manipulation leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-223744.
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 confidenceA cross-site scripting (XSS) vulnerability exists in Rebuild CMS versions up to 3.2.3 in the /feeds/post/publish endpoint. An attacker can inject malicious scripts through unspecified vectors in this functionality, which executes in the context of other users' browsers.
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.2.3CVSS 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.
-
Identify Rebuild CMS installation and versionLocate the CMS installation directory or check the administrative dashboard for the installed version number. Common paths include the web root where Rebuild CMS is deployed. The version is typically displayed in the admin interface footer or in a version file within the installation.Affected if The installed version is 3.2.3 or any version lower than 3.2.3
-
Confirm version is within affected rangeCompare your identified version against the affected range: Ruifang Tech Rebuild CMS version 3.2.3 and below. If your version is exactly 3.2.3 or any earlier release, it falls within the vulnerable range.Affected if The installed version is less than or equal to 3.2.3
-
Verify the /feeds/post/publish endpoint existsAccess your Rebuild CMS web application and navigate to or request the /feeds/post/publish endpoint. This is typically found in the feeds or publishing section of the CMS where posts can be submitted. Check if the endpoint responds to requests.Affected if The /feeds/post/publish endpoint is accessible and responds to requests in your CMS installation
-
Check if endpoint accepts user input without sanitizationSubmit a test payload through the /feeds/post/publish endpoint, such as a simple HTML tag or script alert, and observe if the input is reflected back in the response without encoding or sanitization. This requires functional testing of the endpoint.Affected if User-supplied input in the /feeds/post/publish endpoint is reflected in responses without proper encoding or input validation
Your environment is affected if Rebuild CMS version 3.2.3 or lower is installed and the /feeds/post/publish endpoint is accessible and processes input without sanitization.
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 dataUpgrade Rebuild CMS to a version beyond 3.2.3 that includes the security patch, or implement input validation and output encoding on the /feeds/post/publish endpoint to neutralize malicious script payloads.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1613 — 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-2023-1613 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