dbcve.org
EasypublishApplication · Myiosoft

CVE-2008-3343

HIGH · 7.5 CVSS v2.0 Published 2008-07-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
SQL injection vulnerability in staticpages/easypublish/index.php in MyioSoft EasyPublish 3.0tr (trial edition) allows remote attackers to execute arbitrary SQL commands via the read parameter in a search action.

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 confidence

SQL injection vulnerability in MyioSoft EasyPublish 3.0tr allows remote attackers to execute arbitrary SQL commands via the 'read' parameter in the search action of staticpages/easypublish/index.php. User-supplied input is directly concatenated into SQL queries without proper sanitization or parameterized query usage.

MitigationReplace dynamic SQL query construction with prepared statements/parameterized queries, or implement input validation and output encoding for the 'read' parameter. Apply the principle of least privilege to the database account used by the application.

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
EasypublishApplication
Affected:= 3.0

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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Identify if MyioSoft EasyPublish is installed
    Search the web root directory for files named 'easypublish', 'index.php', or directories containing 'easypublish' in the path. Look for the application banner or version file if accessible.
    Affected if The application MyioSoft EasyPublish is present on the system.
  2. Determine the installed version of EasyPublish
    Locate any version information files, headers, or footer files within the EasyPublish installation. Check the main index.php or configuration files for version strings like '3.0' or '3.0tr'.
    Affected if The installed version is exactly 3.0 (or 3.0tr).
  3. Verify the vulnerable script file exists
    Check for the existence of the file 'staticpages/easypublish/index.php' within the web root. This is the specific file containing the vulnerable search functionality.
    Affected if The file staticpages/easypublish/index.php exists on the server.
  4. Check if the search feature is enabled and accessible
    Attempt to access the search functionality via HTTP request to the affected script. Look for URLs containing the 'search' action or the 'read' parameter pattern in the application's routing.
    Affected if The search functionality is accessible and the 'read' parameter can be supplied via HTTP GET or POST requests.
  5. Identify if user-supplied input reaches the SQL query
    Review the application configuration or database connection settings to confirm that the search feature processes user input without parameterized queries. This typically requires source code review if accessible.
    Affected if User input from the 'read' parameter is directly concatenated into SQL queries without sanitization or prepared statements.

The environment is affected if MyioSoft EasyPublish version 3.0 is installed, the vulnerable script staticpages/easypublish/index.php exists, and the search feature with the 'read' parameter is accessible without input sanitization.

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

Replace dynamic SQL query construction with prepared statements/parameterized queries, or implement input validation and output encoding for the 'read' parameter. Apply the principle of least privilege to the database account used by the application.

Fix this in Easypublish Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-3343 — 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-2008-3343 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