CVE-2023-3755
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 Creativeitem Atlas Business Directory Listing 2.13 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /home/filter_listings. The manipulation of the argument price-range leads to cross site scripting. The attack can be launched remotely. The associated identifier of this vulnerability is VDB-234427. NOTE: 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 · high confidenceA stored cross-site scripting (XSS) vulnerability exists in the filter_listings functionality of Creativeitem Atlas Business Directory Listing 2.13. The price-range parameter accepts unsanitized user input, allowing remote attackers to inject malicious JavaScript code that executes in the browsers of other users viewing the affected page.
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= 2.13CVSS 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 Creativeitem Atlas installationCheck your web application directory for the presence of Creativeitem Atlas files, typically found in the plugins or modules directory of your CMS (check for atlas or creativeitem folder names in your document root)Affected if Creativeitem Atlas Business Directory Listing software is installed on the server
-
Identify the installed versionLocate the version file or readme within the Creativeitem Atlas installation directory; common locations include version.php, readme.txt, or the main plugin/module metadata fileAffected if The installed version is exactly 2.13
-
Verify filter_listings functionality existsSearch the codebase for the filter_listings function or filter_listings.php file within the Atlas plugin/module directoryAffected if The filter_listings functionality is present in the installation
-
Check if price-range parameter is exposedReview the filter_listings code to determine if the price-range parameter is accepted as user input via GET or POST request parameters; look for $_GET['price-range'] or $_POST['price-range'] in the codeAffected if The price-range parameter accepts user input without sanitization
-
Test for XSS vulnerability existenceIf you have access to a test environment, submit a benign XSS payload (such as <script>alert(1)</script> or <img src=x onerror=alert(1)> ) in the price-range parameter through the listing filter form, then view the listing page to see if the payload executesAffected if The payload is rendered unescaped in the browser output
You are affected if Creativeitem Atlas version 2.13 is installed and the filter_listings functionality with its price-range parameter is accessible to users.
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 proper input validation and output encoding for the price-range parameter in the filter_listings function. Sanitize or reject special characters typically used in XSS attacks (<, >, ', ", script tags).
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3755 — 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-3755 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